9

Is there any way of making a single NuGet package that contains binaries targeting x86 ARM x64 etc. so that VisStudio/MSBuild will pick up the correct binaries for each given build configuration?

I can only see support for os target - i.e. Windows, Windows8, win, win8, wp, wp7, WindowsPhone, WindowsPhone7, silverilght4-wp71, wp71, WindowsPhone71 etc.

And you end up with a folder structure like this:

\content
    \net11
    \MyContent.txt
    \net20
        \MyContent20.txt
    \net40
    \sl40
        \MySilverlightContent.html

\tools
    init.ps1
    \net40
        install.ps1
        uninstall.ps1
    \sl40
        install.ps1
        uninstall.ps1

Do I really have to do some powershell-script or pre-build step to accomplish this? It seems like this should be supported by NuGet out-of-the-box?

If I do have to use a script - does anyone have good example code? A ps1 script or some sort of build hook?

I also found this work item on the subject: http://nuget.codeplex.com/workitem/679. But its been around since June 2011, last commented in July.

Any ideas?

Many thanks, Jon

Sources:

auselen
  • 25,874
  • 4
  • 67
  • 105
Jon Rea
  • 8,539
  • 3
  • 26
  • 33

1 Answers1

4

As far as I know, this is still unsupported.

This SO question has two answers that should work for you, one for addressing this with a single package, the other a simple multipackage solution:

How should I create or upload a 32-bit and 64-bit NuGet package?

Community
  • 1
  • 1
kiprainey
  • 3,162
  • 3
  • 26
  • 28
  • I think this is still the case according to this issue: [Add 1st class support for assembly platform (x86, x64, ARM, Any CPU)](http://nuget.codeplex.com/workitem/679) which is still "Proposed" – Carl G Aug 23 '13 at 23:54
  • Apparently this is *still* unsupported. Vote for it at http://nuget.codeplex.com/workitem/679 – Jedidja Jul 24 '14 at 14:24