Tracking: .NET Core Sdk in Build Tools Installer

[debanne]

After installing Build Tools for Visual Studio 2017 RC (download URL: vs_BuildTools.exe), MSBuild.exe cannot be directly used because the Sdks are missing. A workaround is to provide them thanks to the MSBuildSDKsPath variable:
$ set MSBuildSDKsPath=C:\Program Files\dotnet\sdk\1.0.0-rc4-004771\Sdks

Are Build Tools supposed to be used for .NET Core?
If this is the case, then the MSBuildSDKsPath variable should be better documented.
If not (because they are replaced by .NET CLI?), it could be mentioned in https://www.visualstudio.com/downloads/#d-build-tools.

[rainersigwald]

No, the Build Tools installer doesn't currently cover .NET Core scenarios. At some point in the future I hope we can have a .NET Core checkbox within it, but that's not done at the moment.

The dotnet SDK installer (with the CLI) doesn't replace the Build Tools installer, but it is the best current analog for it in some situations, like "what should I install on my CI server?" It is reasonable to install both.

/cc @srivatsn

[rainersigwald]

Changing this to a tracking issue for "there should be a .NET Core checkbox in the Build Tools installer". The actual work will probably happen in the internal VS repo.

[rainersigwald]

Related: NuGet/Home#3660 (getting NuGet restore into the Build Tools installer).

[Spongman]

this is terrible. what's the point of the Build Tools installer, if it isn't to install tools required to build .NET projects?

this is a regression, too. building dotnet core apps worked fine with the v14 build tools. again, this is a breakage of an existing, deployed-to-production scenario.

now we have the v15 tools looking for "Sdk.props" in one directory, and the dotnet SDK isntalling it into some completely different directory.

it's as if one hand isn't talking to the other.

really sloppy guys, really sloppy.

[mariusGundersen]

The solution to using msbuild to compile vs2017 csproj files is to not use msbuild, but to use dotnet instead. So on the build server you need ot install the dotnet sdk, since it comes with the sdks needed by the new vs2017 csproj file, and it comes with nuget. The msbuild install does not.

So, instead of

"C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe" continuousIntegration.msbuild /t:deploy

Use

"C:\Program Files\dotnet\dotnet.exe" msbuild continuousIntegration.msbuild /t:deploy

[evil-shrike]

What about asp.net core projects targeting .net framework (not .net core). Can such solutions be built with vs2017 built tools?

[mariusGundersen]

Not out of the box. You have to copy/paste the sdk folder from a machine that has vs2017 installed to the ci machine, and then it's probably a good idea to put them in the location where msbuild is looking for them, instead of messing about with environment variables.

[evil-shrike]

it's probably a good idea to put them in the location where msbuild is looking for them

and where is it?

[mariusGundersen]

Copy the contents of this folder:

C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\Sdks

To

C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\Sdks

[dasMulli]

Instead of copying over the SDK files, you should also be able to set an MSBuildSDKsPath environment variable to your C:\Program Files\dotnet\sdk\1.0.0\Sdk folder in your CI setup (if the CLI is installed).

[ntregillus]

gotta say, msbuild's loose dependencies lead to so many headaches... it looked like the single responsibility principal was getting followed with the independent with the dotnet tools, but we just took a step back to the msblob that rules them all... who decided the csproj solution was fully baked? please tell them this is an absolute pain.

Please solve this problem: (1) Installing Visual Studio Professional Enterprise (2) Changing the path of 'C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\Sdks' to 'C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Sdks' (Professional o Enterprise) (3) Build the solution