-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Update target frameworks for Microsoft.Microsoft.CodeAnalysis.EditorFeatures.Text #45023
Conversation
src/EditorFeatures/Text/Microsoft.CodeAnalysis.EditorFeatures.Text.csproj
Outdated
Show resolved
Hide resolved
@@ -4,7 +4,7 @@ | |||
<PropertyGroup> | |||
<OutputType>Library</OutputType> | |||
<RootNamespace>Microsoft.CodeAnalysis.Text</RootNamespace> | |||
<TargetFrameworks>net472;netcoreapp3.0</TargetFrameworks> | |||
<TargetFrameworks>$(RoslynPortableTargetFrameworks)</TargetFrameworks> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Personally I think we should go the other way and just delete this property. Having the property is only really valuable for the one time a year where we change the .NET Core TFM. That impacts basically ... me and it's a trivial search replace operation. The downside of having the property is it makes our projects look less like standard projects that customers define. I think it's clearer to just have the TF directly in the project file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm fine going either way. However, any objection to filing a follow-up issue to inline this property since everything is currently uniform and the build passed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's fine by me
No description provided.