.NET 9 Preview 2 #9217
Replies: 13 comments 20 replies
-
|
So where is exact list of changes/new features/etc that come in preview 2? Old way with blogs and separate github issues for each preview before it was even out was so much better... |
Beta Was this translation helpful? Give feedback.
-
The first link in this discussion leads to release notes. Those release notes are also included in the "what's new in" documentation as well. We are still exploring this new approach, thanks for the patience. 
|
Beta Was this translation helpful? Give feedback.
-
This was really confusing for me. This whole post is about ".NET 9 preview 2", but the section "What's new" is about .NET 9 in general. It would be clearer if these links were a direct link to updates of .NET 9 preview 2. For example: to get to the runtime changes, you have to click "detailed release notes", then click on "runtime.md" because nowhere in the README.md is it clear where you can find the runtime changes. While there is a link in the README.md with "Libraries and runtime Announcement", it goes to the announcement post and not the actually changes. All in all, it feels messy compared to the blog posts we had in devblogs.microsoft.com. Hopefully in preview 3 it'll get better. 😅 |
Beta Was this translation helpful? Give feedback.
-
|
@GerardSmit Let me work with our documentation team to see if there's a way to provide sections in the what's new docs specifically for each preview. i.e. what's new in p1, p2, etc. The current release notes tries to do that in detail, but it sounds like it is confusing. We will work to make it right. |
Beta Was this translation helpful? Give feedback.
-
|
I usually check the API diffs for new features/changes - would be nice to see them being posted earlier, though (since it usually takes around 1-2 weeks for them to show up). |
Beta Was this translation helpful? Give feedback.
-
|
I have made adjustments to the format to make it much more streamlined. |
Beta Was this translation helpful? Give feedback.
-
|
Most of the links either lead back here or to Preview 1 announcements. What's new in .NET 9 is aggregated so checking out what's new in Preview 2 requires one to see the git history of the file. The old system was way more convenient. For future readers: dotnet/docs@e1fa640 |
Beta Was this translation helpful? Give feedback.
-
|
Would it be easier if these what's new docs had sections for each preview or similar? The current diffs can be found in the release notes: https://github.com/dotnet/core/tree/main/release-notes/9.0/preview |
Beta Was this translation helpful? Give feedback.
-
|
@JonDouglas None of the files that actually contain the relevant information (sdk.md, runtime.md and so on) are actually linked anywhere in the markdown documents themselves which is confusing. |
Beta Was this translation helpful? Give feedback.
-
|
I hear you. I'll bring this up to the team. It is a bit confusing. Thanks for the feedback. |
Beta Was this translation helpful? Give feedback.
-
|
this is so badly done, there are so many links and then you don't know exactly what has been changed or added because we are redirected to the documentation page. the devblog was much easier and better to understand. |
Beta Was this translation helpful? Give feedback.
-
|
The blog way was "OK", this is just heck too confusing |
Beta Was this translation helpful? Give feedback.
-
|
Thank you all for your feedback on this process and being patient with our team as we're experimenting with different ways of communicating. We will re-assess in the meantime and bring more clarity by the next preview. For now, changes can be found in both the release notes and what's new pages. I will make notes to ask our product and documentation teams to provide clear "diffs" of what has changed in each preview beyond the current structure of release notes which it sounds is too many clicks and not as centralized like the blogs were. If there are certain things you would like to see from us as the community, please let us know so we can bring it up as well. Feedback as simple as "go back to the way it was" or how we can integrate some of these new concepts better are all fair game. We are listening and will adjust accordingly. Thanks for your patience. |
Beta Was this translation helpful? Give feedback.
-
|
I don't have enough time for a deep dive with clicking links that lead me away from the main announcement. The old format was great because I got to see all new features for that preview in one place, preferably with a code example. I would prefer the announcement centralized, so I can read it without clicking on links, or, at most one link deep. Main announcement:
For that specific preview #, not a link to a general description for the whole .NET 9! |
Beta Was this translation helpful? Give feedback.
-
|
you don't even have to change anything on github, just keep publishing .net as it was on the devblog page, put links to the github there and problem solved. it's just too confusing for some people, you have to search through all the documentation to find out what's new or changed. the .net monthly updates are still published on the devblog, why not everything else... |
Beta Was this translation helpful? Give feedback.
-
|
If you could try reading the release announcement in the GitHub app on a phone and try following all the links it might be helpful. In a perfect world I'd like it if any links I have to click through to read the details of this specific preview release should keep me in the app. Trying to read this announcement today kept switching me into the browser and I wasn't convinced it was actually sending me to the right pages. That said it would be easier not to have to click through links at all. |
Beta Was this translation helpful? Give feedback.
-
|
so, is .net dead? |
Beta Was this translation helpful? Give feedback.
-
|
Obviously (based on the feedback here), the most requested links are the Team Announcements and their related release notes. There should be no other links above these except in the general short introduction. Also, the note that "Announcement links will be populated throughout the release day" is very confusing. I think that this general announcement should not be posted until those announcements are already published. If Team Announcements are the first header and they include direct links to the respective release notes it would be much clearer. Example of how this post could start: We are pleased to announce the release of the second preview of .NET 9, along with comprehensive release notes that highlight significant enhancements from the initial preview. Additionally, we have previously outlined Our Vision for .NET 9, which describes some of the broad areas we intend to deliver on by the upcoming November 2024 release. Team Announcements for Preview 2
You can find detailed release notes about the new features in .NET 9 Preview 2 and up-to-date What's new in .NET 9 and Breaking Changes in .NET 9 in .NET docs. The latest .NET 9 release is always available at dotnet.microsoft.com and .NET 9 Releases. etc etc |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the feedback here and I agree, going to make this adjustment ;) |
Beta Was this translation helpful? Give feedback.
-
|
The new |
Beta Was this translation helpful? Give feedback.
-
|
BTW, there are incorrect dates at https://github.com/dotnet/core/blob/main/release-notes/9.0/README.md#releases Years show 2023 instead of 2024. FYI |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! Sent PR, also feel free to submit a PR if you see anything else. |
Beta Was this translation helpful? Give feedback.
-
|
I don't see anything in here about assembly saving in |
Beta Was this translation helpful? Give feedback.
-
|
Take a look at Preview 3 where some additional work has been done around |
Beta Was this translation helpful? Give feedback.
-
|
There might be a PR pending perhaps but it looks like release notes just links back to itself? Other than looking at the commits for certain tags will there still be a way to know what's coming in a preview before it officially drops? I loved this kind of format -> #8133, and it helped me decide to pull down the daily's or not. I get issues isn't the correct format here but some page dedicated to what's new specifically in preview X as features are merged (as opposed to released) would be amazing for the enthusiast. |
Beta Was this translation helpful? Give feedback.
-
|
Made adjustments here to this post and also the main readme landing. Reached out to you on X as well to further the discussion. |
Beta Was this translation helpful? Give feedback.
-
|
Was also wondering where the post on the .Net Blog where? So this is the new way of announcing previews, no more .net blog posts? Can you resume the posts on the .net blog which go directly in my RSS feed in Outlook? These posts keep me hyped and informed and I think are a perfect Marketing tool. Same for the .NET Blog, without the Preview posts the blog becomes pointless |
Beta Was this translation helpful? Give feedback.
-
|
For .NET 9 previews we are utilizing GitHub Discussions to make announcements. For more information #9131. |
Beta Was this translation helpful? Give feedback.
-
|
In each opportunity, blog, youtube video, or whatever Microsoft does, at the end they ask for Feedback, nevertheless, when the community screams with feedback it seems that MS is not so responsive. The whole page scream for the return to the Devblogs way, that was is really much more better. I am not sure what is the perceived (or imagined) value MS saw in relinquishing the Devblogs way. I hope this will be undone as soon as possible. |
Beta Was this translation helpful? Give feedback.
-
"Everybody is conservative about what they know best." -- Robert Conquest's first law. |
Beta Was this translation helpful? Give feedback.
-
|
@masonwheeler Thank you very much, I really liked the quote and I learned a new thing from you, really appreciate it, this quote will stay with me for a very long time ❤️, the best reply I ever got ❤️ |
Beta Was this translation helpful? Give feedback.
-
|
Based on feedback and working directly with folks on this thread we vastly updated the post from it's original form. Many of the comments were around being able to more easily find links directly to the release notes, high level overview summary, and links for RSS feed. These have all been incorporated. I even got on calls with folks to better understand how we can improve this. This new format is reflected here in the updated post and also in the Preview 3 post, on the main READMEs in the repo, and more. We are listening as it comes to feedback around posting each release on the .NET Blog. Like any good experiment you have to give it time to actually attempt to work to gather feedback, iterate, and make decisions going forward. So trust me, myself and the team are paying very close attention to every single comment and making tweaks and adjustments as we go. |
Beta Was this translation helpful? Give feedback.
-
We are pleased to announce the release of .NET 9 Preview 2.
This release contains the following Runtime & SDK improvements:
For details on these new features and more see the Runtime Release Notes and SDK Release Notes
You can find detailed release notes for additional features in .NET 9 Preview 2 below:
Get started
To get started with .NET 9, install the .NET 9 SDK.
If you're on Windows using Visual Studio, we recommend installing the latest Visual Studio 2022 preview, or get started with Visual Studio Code and the C# Dev Kit extension.
You can find .NET 9 Preview 2 Installer & Binaries on GitHub.
Team Announcements & Discussions
Discuss this release with the product teams on GitHub through the announcements for this release.
Stay up-to-date with .NET 9
You can stay up-to-date with all the features of .NET 9 with:
For .NET 9 previews we are utilizing GitHub Discussions to make announcements. For more information read our discussion.
Stay up to date by subscribing to the RSS feed for all release announcements.
Beta Was this translation helpful? Give feedback.
All reactions