What's new in .NET 9 Preview 2

[JonDouglas]

To add content, fill out the following template as a new comment on this issue. Last day to submit content is the Friday before release.

## Contribution Template - Use to your discretion

Feature Name: [Short title of the feature]

What It Does: [Brief description of the feature]

How It Helps: [Explain the benefit or problem it solves]

How to Use: [Simple instructions on using the feature]

Future Plans: [Any upcoming updates for this feature, if any]

Documentation: [A link for readers to learn more]

Index of .NET 9 releases

• What's new in .NET 9 Preview 1 #9089
• What's new in .NET 9 Preview 2 #9090
• What's new in .NET 9 Preview 3 #9091
• What's new in .NET 9 Preview 4 #9092
• What's new in .NET 9 Preview 5 #9093
• What's new in .NET 9 Preview 6 #9094
• What's new in .NET 9 Preview 7 #9095
• What's new in .NET 9 RC 1 #9096
• What's new in .NET 9 RC 2 #9097

[Varorbc]

Why is it closed?

[slang25]

Why is it closed?

See here: #9131 (reply in thread)

[richlander]

Yes. We're doing this a different way.

You'll likely see these show up in a branch on this repo before too long, for Preview 2. There is no intent to reduce transparency and engagement. Doing this via issues did not serve content quality. Most would people would agree that issues are not intended for how we were using them. This is content we intend to commit to source control so should use a PR flow.

If it would help, we can consider opening Preview issues that point people to where things are happening, that we close when the preview ships.

[Securso]

I'm using the previews for .Net 9 (as I did for previous releases). We are now half way to preview 2 and nothing has been added to this page. Does this mean there is going to be very little in preview 2.

[slang25]

I'm using the previews for .Net 9 (as I did for previous releases). We are now half way to preview 2 and nothing has been added to this page. Does this mean there is going to be very little in preview 2.

So what used to happen was this issue would get updated typically towards the end of a preview release cycle, maybe half of the details added in the last week while other parts come in as they are ready.

Going forwards, these issues are closed and are no longer the way to collect the new features for a release. You can read the plan here:
#9131

If you want to get notifications on new releases then you can subscribe to the announcements repo for new issues (which will only contain announcements), or the core repo discussions. For an early look at release notes, you could spy on the branches / PRs in this repo, which will exist soon before the announcements (presumably).