Jeff Kluge
Jeff Kluge
I don't know of one yet. It would be great to add to this API though.
Does `ImageProgressCallback` do something special? Is the managed DISM API here on the callstack for the exception?
This line is probably throwing: ```c# MoHelper.ProgressBar.Value = progress.Current; ``` I'm not sure why but the DISMAPI value for progress.Current is not always 0-100. If you want to safely calculate...
Since this library is just a wrapper around the native API, we'd have to figure out if the native API supports that. There used to be some documentation around WIMGAPI...
I'm not sure if I did that deliberately. I wonder if I changed it now it would break anyone? Do you feel pretty strongly about changing it?
@SymbioticKilla unfortunately I do not. I would imagine some new functionality shipped in `dismapi.dll` which isn't on your Windows Server 2016 machine. Are you able to try on a newer...
I think you can use [ManagedWimgApi](https://github.com/jeffkl/ManagedWimgApi) to call [GetMountedImageInfo()](https://github.com/jeffkl/ManagedWimgApi/blob/main/src/Microsoft.Wim/WimgApi.GetMountedImageInfo.cs#L42) which will return all of the mounted images and their status. Then you can use other APIs there to unmount it...
Similar to https://github.com/jeffkl/ManagedDism/issues/36, this API is just a wrapper around the native API. `dism.exe` has logic to enumerate files in a folder and call `AddPackage` multiple times. You'll need to...
Yeah it really is annoying that some other package is depending on NuGet.Frameworks and then since its considered a runtime dependency, the wrong version ends up next to your assembly....
@craigktreasure yeah that's probably a good idea at the very least. I wonder if I should add the workaround for all "unit test" projects which are probably pulling in the...