```
MagickNet.Initialize();
// MagickNet.Initialize(Path.Combine(AppDomain.CurrentDomain.BaseDirectory, "imagemagick"));
using(var collection = new MagickImageCollection("test.pdf")) {
// throws
}
```
Ghostscript is installed via the official package (both x86/x64).
The strange thing that i do not have this problem with our own implementation. We are currently
in the process of switching this one out with yours :)
By the way, it would be interesting if we could create separate nuget Ghostscript package with required
dependencies (gswin32.exe & friends bundled).
Would that violate the ghostscript license? Because then you could just use the new feature in Nuget 2.5 to
copy those dependencies into $(OutputPath) upon each build. What do you think? Would be awesome
to have PDF-support out of the box, without installing some thirdparty msi.
If the license agreement is not violated, we would have to patch ImageMagick so that it stops
looking in the registry for a valid ghostscript path.
I doubt this patch would be accepted upstream though.
What do you think?
Comments: ** Comment from web user: dlemstra **
MagickNet.Initialize();
// MagickNet.Initialize(Path.Combine(AppDomain.CurrentDomain.BaseDirectory, "imagemagick"));
using(var collection = new MagickImageCollection("test.pdf")) {
// throws
}
```
Ghostscript is installed via the official package (both x86/x64).
The strange thing that i do not have this problem with our own implementation. We are currently
in the process of switching this one out with yours :)
By the way, it would be interesting if we could create separate nuget Ghostscript package with required
dependencies (gswin32.exe & friends bundled).
Would that violate the ghostscript license? Because then you could just use the new feature in Nuget 2.5 to
copy those dependencies into $(OutputPath) upon each build. What do you think? Would be awesome
to have PDF-support out of the box, without installing some thirdparty msi.
If the license agreement is not violated, we would have to patch ImageMagick so that it stops
looking in the registry for a valid ghostscript path.
I doubt this patch would be accepted upstream though.
What do you think?
Comments: ** Comment from web user: dlemstra **
Your are compiling my code into your project? Maybe you should add 'image->debug(true)' at line 177 of MagickReader.cpp (changeset 26302). You should get a lot of extra information when you run the code with a debugger attached.