Dmitry, we are having a great deal of pain with ImageMagick when mixing projects that require
either the x86 or x64 version of ImageMagick.
Therefor i propose a change in both nuget and naming convention to MagickNet assembly. The reason for this is that a direct dependant project might overwrite Magick.Net.Dll (x86) with it's own copy of Magick.Net.Dll (x64). Atleast by having a separate naming convention it does not matter
if they overwrite one another!
x86:
Rename Magick.Net.dll-> Magick.Net.x86.dll
Copy dependencies ImageMagick\x86
x64:
Rename Magick.Net.dll -> Magick.Net.x64.dll
Copy dependencies Imagemagick\x64
Change Initialize() from ImageMagick\x86|x64
By making this change you would make it a hell of a lot easier for us doing this inter-mixing :) Judging
by the number of discussions this would be a welcomed change for most people so ;
Comments: ** Comment from web user: petersunde **
either the x86 or x64 version of ImageMagick.
Therefor i propose a change in both nuget and naming convention to MagickNet assembly. The reason for this is that a direct dependant project might overwrite Magick.Net.Dll (x86) with it's own copy of Magick.Net.Dll (x64). Atleast by having a separate naming convention it does not matter
if they overwrite one another!
x86:
Rename Magick.Net.dll-> Magick.Net.x86.dll
Copy dependencies ImageMagick\x86
x64:
Rename Magick.Net.dll -> Magick.Net.x64.dll
Copy dependencies Imagemagick\x64
Change Initialize() from ImageMagick\x86|x64
By making this change you would make it a hell of a lot easier for us doing this inter-mixing :) Judging
by the number of discussions this would be a welcomed change for most people so ;
Comments: ** Comment from web user: petersunde **
I've not tested running in the same domain, but you are probably correct about it not going to work. I'm curious though if it would work running in seperate domains. Anyway, it would be a good idea
to change the name and output folder structure to avoid confusion.
Hehe, i missread your name ;)