Many .NET projects do not target an explicit CPU architecture (i.e x86/x64) and managing two seperate
builds can be a pain (especially if you do not rely on x64 specific features). A web project is a great example
where most projects targets AnyCpu. By using a seperate bootstrapping dll you would not
need to worry about cpu architecture targeting.
You can find a great example [here](http://stackoverflow.com/questions/108971/using-side-by-side-
assemblies-to-load-the-x64-or-x32-version-of-a-dll).
NB! Keep the x86/x64 packaging, but provide an additional AnyCpu nuget package.
Comments: ** Comment from web user: dlemstra **
builds can be a pain (especially if you do not rely on x64 specific features). A web project is a great example
where most projects targets AnyCpu. By using a seperate bootstrapping dll you would not
need to worry about cpu architecture targeting.
You can find a great example [here](http://stackoverflow.com/questions/108971/using-side-by-side-
assemblies-to-load-the-x64-or-x32-version-of-a-dll).
NB! Keep the x86/x64 packaging, but provide an additional AnyCpu nuget package.
Comments: ** Comment from web user: dlemstra **
It turns out that it is not as easy as described in the link you posted. It will probably be to confusing for the user of Magick.NET. You have to add a reference to both the x86 and the bootstrapper dll. That will result in a compiler warning because you are trying to use a x86 library in a AnyCPU dll. I think it is better to create some kind of wrapper that will call a method from either the x86 or the x64. And I am not even sure if that is possible. If you can provide me with a simple example project that does what is described in your link feel free to contact me. I will move this issue to the next release and see if I can create some kind of prototype with a wrapper library.