Support package managers about msbuild

[AndyGerlicher]

Package support is on our long term roadmap. This is not something we want to address at this time.

[lilith]

Keep in mind, that with this you're killing F# (for which NuGet is unusable) and cross-platform C#+p/invoke (where NuGet is unusable).

After so many promises to play fair, this is pretty much the ultimate F*** you to the OSS community.

Is permitting re-load after pre-build so hard?

[dsplaisted]

Is permitting re-load after pre-build so hard?

@nathanaeljones Basically, yes. The newly imported targets could impact everything that's already been evaluated and executed, so MSBuild would have to throw out everything and start over.

Generally what we do for package restore for CI / command line builds is to have an outer project which runs package restore and then calls MSBuild on the project files that actually build the source code. These projects aren't evaluated until after packages are restored, so it works correctly. Here's an example of this.

This doesn't help in Visual Studio because VS wouldn't build the outer project which does package restore. However, what you can do is to have the project do the package restore and then call MSBuild on itself. I've created a proof of concept of doing this in the paket.targets file here.

[dhusemann]

Shouldn't this stay open?? although it isn't in the current plans it is still something to be addressed.