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: mg_mercell **
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: mg_mercell **
This would be wery helpfull to us, when is this planned to be implemented?