Support .NET packages for C++/CLI

[fubar-coder]

One of the problems with C++/CLI is, that NuGet only allows the installation of native DLLs for C++(/CLI), but not .NET assemblies.

My proposal is, that when we have a C++/CLI configuration, that the installation of .NET packages/assemblies is allowed. If there are other non-CLI configurations, a warning should be shown. Currently, it's a PITA using the install.ps1/uninstall.ps1 scripts and it's unreliable too, because the object model might change between VS versions and therefore break installing/updating NuGet packages.

EDIT: This is loosely related to #300

[yishaigalatzer]

Indeed there is no proper support for C++ projects, the scope of the issue however is much larger than what is described here, in some sense C++ projects are a different world than .NET with a different set of constraints.

We do plan to go deeper into this designing this with the C++ team, so keeping this around as a marker issue, and will replace it with more of a design document on the wiki once things start moving in earnest.

[ddrinka]

I've noticed that installing managed assemblies into C++/CLI is possible with a project.json dependency configuration, as opposed to the legacy packages.config. Moving to the new dependency model fixed this issue for us, without requiring any adjustment to our development workflow.

[emgarten]

Duplicate of #5292

[davidjward30]

I see this is closed, yet marked as a duplicate of itself?

[emgarten]

@davidjward30 good catch, I updated the issue number 😄