Commented Unassigned: Change in nuget deployment structure [979]

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: dlemstra **

Have you tried running code that use both the x86 and x64 version in the same application domain? I don't think this will work. When the ImageMagick dll are being loaded it might find the wrong version. I do agree with you that it might be easier to determine which version of Magick.NET you are using. But if this will result in loading the wrong version of the ImageMagick dll's we should probably keep it this way.

p.s. who is Dmitry?