Open gordonwatts opened 10 years ago
How about packages that pivot on platform but can be imported by managed projects? I haven't spent any quality time in raw NuGet yet but I don't see pivots as a concept they get. Picture a native library with an interop assembly, or maybe a managed assembly with distinct platform-specific instances. You want to copy the binaries to the platform-specific output folder and also resolve references to the right instance. In C++/CLI, C#, and VB.NET projects.
MSBuild makes my brain hurt.
Including auto-package C++ libraries into a managed C++ project causes a mess in the settings. The most obvious evidence of this is after the inclusion, all references show up as a "!" in the CLI, even though it seems to build ok. Worse, it is no longer possible to use the VS GUI to add new assemblies.