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.
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
Target on .NET 8.0 #365
Target on .NET 8.0 #365
Changes from 1 commit
47a57c5
56586fa
b6a55cb
df400e2
ec3d52d
bd5bc9d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Should probably do the 8.- packages here.
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 follow the previous one.
https://github.com/microsoft/FeatureManagement-Dotnet/blob/main/tests/Tests.FeatureManagement/Tests.FeatureManagement.csproj#L28
Should I also change them to 6.- and 7.-?
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 think yes, if it doesn't cause any issues. These are the test packages so they don't matter for customers, so we might as well be on latest.
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 think we are good to use "net8.0", this is the correct TFM according to doc.
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.
Sorry, my comment might have been misleading. I meant we should do
I didn't know what the latest sub-versions of the TestHost and Json packages were so I only wrote the "8.-" part. 😅
When you said
I thought you were also talking about the json and testhost packages. Which I said yes because .net6 should use the 6.~~~ packages, .net7 should use the 7.~~~ packages and 8 use 8.~~~
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.
The latest version of Microsoft.Extensions.Configuration.Json package is 8.0.0. It seems like there is no minor/patch version bump since 3.1.32. It is quite stable. So It is good for us to use 7.0.0/6.0.0 for .NET 7/6.
The latest version of Microsoft.AspNetCore.TestHost is 8.0.1 and I will also update the version for NET 6 and NET 7.