Skip to content
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 the sample to target net5 #4096

Merged
merged 3 commits into from
Jan 11, 2021

Conversation

vitek-karas
Copy link
Member

It generates warnings because it targets out-of-support 3.0

It generates warnings because it targets out-of-support 3.0
@vitek-karas vitek-karas self-assigned this Jan 8, 2021
@vitek-karas vitek-karas requested a review from a team as a code owner January 8, 2021 13:12
The CI seems to only support .NET 5 and it doesn't really matter for the sample if it's 3.1 or 5.
@vitek-karas vitek-karas changed the title Update the sample to target netcoreapp3.1 Update the sample to target net5 Jan 8, 2021
Copy link
Member

@elinor-fung elinor-fung left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably update the prerequisites for the tutorial that uses this too (maybe with a note that the sample uses 5.0, but support was added in 3.0) - https://github.com/dotnet/docs/blob/master/docs/core/tutorials/creating-app-with-plugin-support.md

@@ -2,7 +2,7 @@

<PropertyGroup>
<OutputType>Exe</OutputType>
<TargetFramework>netcoreapp3.0</TargetFramework>
<TargetFramework>net5</TargetFramework>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The version is called out in the readme too.

@@ -1,7 +1,7 @@
<Project Sdk="Microsoft.NET.Sdk">

<PropertyGroup>
<TargetFramework>netcoreapp2.1</TargetFramework>
<TargetFramework>net5</TargetFramework>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it make sense to add a Directory.Build.props to set TargetFramework for all these projects?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@elinor-fung That's an interesting idea. We're looking at how to update all the samples on the release cadence. See dotnet/docs#22271. Can you add thoughts on how to make that easier on that issue?

@vitek-karas
Copy link
Member Author

@elinor-fung thanks for pointing out the docs update: dotnet/docs#22297

@BillWagner BillWagner merged commit 03fb38a into dotnet:master Jan 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants