-
-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem building SDK-style .NET Framework projects #23
Comments
It looks like the target checks the "$(MSBuildThisFileDirectory)\tools\net46" folder for This folder exists at "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Sdks\Microsoft.NET.Sdk\tools\net46" when Visual Studio is installed, but not at "C:\Program Files\dotnet\sdk\2.0.2\Microsoft\Microsoft.NET.Build.Extensions\tools" (the latter only has a "netcoreapp1.0" subfolder). However, we set the MSBuild extensions folder to the dotnet SDK path if we detect an SDK project. I guess it makes sense that .NET Framework projects should be using the VS build chain. It is called the .NET Core SDK after all. Suspect we'll need to check if the project targets .NET Framework and use the |
Interesting - it looks like the behavior is also different between an SDK project that targets |
MicrosoftMicrosoft.NET.Build.Extensions is used to support .NET Standard 2.0 when targeting .NET 4.6.1 and up. So it's not used if you're targeting .NET 4.6, because that doesn't support .NET Standard 2.0. You should pretty much never use the targets in However, I don't know if you need to explicitly point MSBuild to those targets. MSBuild has a built-in |
@dsplaisted Thanks a bunch, that does help. Especially the bit about a custom resolver. After popping it open in a decompiler I can see how the VS toolchain finds the SDK. Based on what you said about the targets in the VS |
The text was updated successfully, but these errors were encountered: