This repository has been archived by the owner on Mar 22, 2019. It is now read-only.
Find C#/VB targets using MSBuildToolsVersion #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adds support for Visual Studio 2019 by using MSBuildToolsVersion instead of VisualStudioVersion, since they no longer match after dotnet/msbuild#3778.
|
By the way, @wjk, would you mind disconnecting this repo from Microsoft/MSBuildSdks? That way people can file bugs on it directly. |
|
@rainersigwald Thank you for your contribution, but since .NET Core 3.0 was released, the WindowsForms and WPF SDKs in this repository are now obsolete; I have moved over to using |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds support for Visual Studio 2019 by using
MSBuildToolsVersioninstead ofVisualStudioVersion, since they no longer match after dotnet/msbuild#3778.This is a port of novotnyllc/MSBuildSdkExtras#128.
This change does not break Visual Studio 2017 compatibility: there, the two variables have the same value
15.0. In 2019, they differ.