Blocking issues for the conversion of CLI to MSBuild

This issue is meant for tracking all of our external blocking issues that are preventing the CLI to work on MSBuild.

• https://github.com/NuGet/Home/issues/3102 - dotnet restore doesn’t install custom MSBuild targets
• https://github.com/NuGet/Home/issues/3117 - Convert NuGet.BuildTasks to .NET Core (and create a NuGet package for CLI to consume them)
• https://github.com/NuGet/Home/issues/3136 - ResolveNuGetPackageAssets doesn’t handle RIDs correctly
• https://github.com/dotnet/roslyn-project-system/issues/296 - Need to split up ResolveNuGetPackageAssets in MSBuild
• https://github.com/dotnet/roslyn/issues/9640 - Publish a portable tasks+targets nuget package for the compiler build task and use it in the toolset
• https://github.com/dotnet/roslyn/issues/12650 - Create a NuGet package containing CSharp.targets that can build on .NET Core
• https://github.com/Microsoft/msbuild/issues/774 - .nuget.props/.targets are not loaded on .net core
• https://github.com/Microsoft/msbuild/issues/692 - create NuGet packages for MSBuild assets
• https://github.com/Microsoft/msbuild/issues/720 - csc.exe needs a “host” for cross-plat MSBuild. MSBuild should just use the host it is running under
• https://github.com/Microsoft/msbuild/issues/658 - custom Tasks loading dependencies
• https://github.com/Microsoft/msbuild/issues/784 - generic loading .props and .targets files next to the .csproj file (non-NuGet specific)
• https://github.com/Microsoft/msbuild/issues/970 - Excludes against Includes with globs don’t work on OS X
• https://github.com/NuGet/Home/issues/3462 - ToolsRef design

Non-blocking issues, but needed for shipping:

• https://github.com/dotnet/roslyn/issues/12167 - Csc.exe without -nologo requires Microsoft.CodeAnalysis.dll in BaseDirectory
• https://github.com/Microsoft/msbuild/issues/750 - Native image cannot be loaded multiple times
• https://github.com/Microsoft/msbuild/issues/872 - msbuild.exe.config needs to be packaged

[tuespetre]

Would anyone from the ASP.NET team be willing/able to share a rough concept of what dotnet-* tools are going to look like after the move to MSBuild?

[eerhardt]

All of the blocking issues in this list have been checked off. This can now be closed.