Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Tracking: .NET Core Sdk in Build Tools Installer
See original GitHub issueAfter 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.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:21
- Comments:38 (14 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
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.
I think you are missing what the intent of my ask: I shouldn’t need visual studio installed on my build machine: I should only need msbuild to build my project, not a full IDE