Skip to content

Update to .NET 9.0 RC2 #852

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 2 commits into from
Oct 18, 2024
Merged

Update to .NET 9.0 RC2 #852

merged 2 commits into from
Oct 18, 2024

Conversation

KyleMcMaster
Copy link
Collaborator

@KyleMcMaster KyleMcMaster commented Oct 17, 2024 •
edited
Loading

Re: #848

This pull request includes several updates to upgrade the project from .NET 8.0 to .NET 9.0 and to update various package versions. The most important changes include updating the .NET SDK version, changing the target framework, and updating multiple package versions to their latest releases.

.NET Version Updates:

  • Updated .github/workflows/dotnetcore.yml to use .NET SDK version 9.0.100-rc.2.24474.11 (dotnet-version).
  • Updated global.json to specify .NET SDK version 9.0.100-rc.2.24474.11 (version).

Target Framework Update:

  • Changed the target framework in Directory.Build.props to net9.0 (TargetFramework).

Package Version Updates:

  • Updated various package versions in Directory.Packages.props to their latest versions, including:
    • FastEndpoints to 5.30.0.10-beta.
    • Microsoft.EntityFrameworkCore packages to 9.0.0-rc.2.24474.1.
    • xunit.runner.visualstudio to 3.0.0-pre.35.

Project Configuration Update:

  • Enhanced the Microsoft.EntityFrameworkCore.Design package reference in src/Clean.Architecture.Web/Clean.Architecture.Web.csproj to include specific assets (PrivateAssets, IncludeAssets).

Screenshots:

Swagger working:
image

Output from dotnet run -- project src/CleanArchitecture.Web
image

@ardalis ardalis merged commit 195f698 into main Oct 18, 2024
3 checks passed
@aminsharifi
Copy link
Contributor

It is good to use the latest LTS .net version that is .net 8 not a preview of .net 9
@KyleMcMaster & @ardalis

@ardalis
Copy link
Owner

ardalis commented Oct 21, 2024

We're getting ready for net9 release in a couple of weeks. I'd say we could parameterize the version but it only ends up in one file anyway so probably not worth it.

@aminsharifi
Copy link
Contributor

We're getting ready for net9 release in a couple of weeks. I'd say we could parameterize the version but it only ends up in one file anyway so probably not worth it.

In general, do you recommend upgrading to .net 9 or waiting for the next LTS .net version, which is .net 10?

@ardalis
Copy link
Owner

ardalis commented Oct 21, 2024

In general I recommend staying current. Why?

  • It's less painful to keep pace annually and incrementally than to be years behind and try to "catch up"
  • There are bug fixes, performance fixes in every release, so it's a fallacy to think you're somehow "better off" with an LTS release
  • Assuming you follow this strategy consistently, you're still never out of support
  • When's the last time you (dear reader whoever you are) actually opened a ticket with Microsoft for support, vs just finding help through other means, anyway?

@scottrudy
Copy link

In enterprise development there are usually less teams than applications. Some applications may not be touched for a year or more due to competing priorities. The reality of updating every application to a new version every 18 months is unrealistic in my opinion. This is a benefit of LTS releases. If you want to stick with that there's a net8-release branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@KyleMcMaster @aminsharifi @ardalis @scottrudy