Update to net8.0 #276
Open
Update to net8.0 #276
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
.NET 6 is several years old, in fact .NET 9 just came out. I don't actually have a .NET 6.0 SDK on my Linux dev machine, so in order to build FVim I had to update everything to target net8.0 rather than net6.0. (Or hunt for old SDK packages I could install, but it was easier to just update the target frameworks).
Everything built and ran just fine after the update, so I figured I might as well make a PR in case you want to pull this change in.
This doesn't update any NuGet packages, incidentially. There are several packages that
dotnet restorewarns about, so I'll probably make another PR updating those at some point.