Adds x86 and x64 build platforms

[Cronan]

Fixes #9

If your library has x86 or x64 compiled-code and COM dependencies, then an AnyCPU build of ExcelDnaDoc will not work, and throws a 'BadFormatException'.

This change allows x86 and x64 builds.
Samples are not built when choosing x86 or x64

[Cronan]

@govert @augustoproiete

[govert]

@augustoproiete So if my library is mixed code and targets x86, then the ExcelDnaDoc that processes it needs to be x86 itself?

[govert]

Sorry, I meant @Cronan ...

[Cronan]

I’ll find the link where they go into detail, but yes, some libraries will throw if you try to load them into AnyCPU (mine does this)

…

On 31 May 2018, at 17:36, Govert van Drimmelen ***@***.***> wrote: @augustoproiete So if my library is mixed code and targets x86, then the ExcelDnaDoc that processes it needs to be x86 itself? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[govert]

I presume an alternative would be to use something like Mono.Cecil to examine the assemblies.
But that would be a bigger job to tackle, and I'm not sure how typical the mixed assembly case is for Excel-DNA.

[govert]

I guess this means the NuGet spec would need to have platform-specific binaries.
Should I add an issue to track this?

[Cronan]

Some of my dependant assemblies are mixed-mode assemblies, which contain both native and managed code. These cannot be loaded into an AnyCPU assembly - they cannot only be loaded into something with the same bigness as them - x86 or x64. https://msdn.microsoft.com/en-us/library/x0w2664k.aspx

…

On 31 May 2018, at 19:31, Ivan Cronyn ***@***.***> wrote: I’ll find the link where they go into detail, but yes, some libraries will throw if you try to load them into AnyCPU (mine does this) > On 31 May 2018, at 17:36, Govert van Drimmelen ***@***.***> wrote: > > @augustoproiete So if my library is mixed code and targets x86, then the ExcelDnaDoc that processes it needs to be x86 itself? > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub, or mute the thread.

[Cronan]

Yeah, we’ve bumped into the NuGet issue before, good idea to add an issue. I think this is a real minor case, I’m just happy not to have to add the extra build targets in manually.

…

On 31 May 2018, at 19:39, Govert van Drimmelen ***@***.***> wrote: I guess this means the NuGet spec would need to have platform-specific binaries. Should I add an issue to track this? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.