[Announcement] ASP.NET Core in .NET 8 is now available!

[wtgodbe]

Hello all,

Today, we released .NET 8, which includes lots of exciting new features and updates in ASP.NET Core - you can read all about it in our blog post! We'd specifically like to thank all of you for your great & numerous community contributions during the .NET 8 cycle - whether that be PRs, community triage, feature suggestions, or bug reports, our wonderful community is instrumental in helping us deliver a great product.

You can find direct links to download .NET 8 here.

Happy coding!

[diegosasw]

There have been breaking changes in AddJwtBearer and the JwtBearerOptions and I can't find any documentation about it. Is there any relevant link? Possibly there is a bug, unless the mechanism has changed #52075

[martincostello]

The specific change referenced doesn't seem to be documented, but the change in the associated issue is related to changes in the AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet repository for version 7, which ASP.NET Core 8 depends on. I had to make the relevant change to use JsonWebToken when updating System.IdentityModel.Tokens.Jwt to 7.0.0-preview and later.

[stefannikolei]

All be aware that using 'JwtSecurityTokenHandler.DefaultInboundClaimTypeMap.Clear();;' does probably not work after upgrading to .net8. 'JsonWebTokenHandler.DefaultInboundClaimTypeMap.Clear();' should be used.

This change could have been documented better.

[blogcraft]

Is there any known issues with error c0000005 in Azure AppService (Windows) using .NET 8? I can't get my app to run. The same app in Linux App Service runs without problem.

[zaneclaes]

Some of us can't even start our app we had built on RC1/RC2 due to mysterious framework errors that are impossible to debug, and we are now are now dead-in-the-water: #52190

I don't understand why breaking changes were made between RC2 and GM (as it appears happened); I must be misinformed about how Microsoft handles release numbering. I have always taken for granted (and it has been true at all my jobs) that the final "release candidate" MUST be identical to the "shipped" version (practically a tautology). Thus I am cautious when using a RC, but I did not practice anywhere near that caution when switching to 8.0.100... and now we're stuck without an easy revert path since we spent the last few days upgrading our build machines, dev machines, etc. when the final release came out.