What's New - .NET 10 Preview 1 #44878
Conversation
CamSoper
requested review from
gewarren,
a team and
BillWagner
as code owners
dotnet-policy-service
bot
added
🏁 Release: .NET 10
Co-authored-by: Genevieve Warren <[email protected]>
Co-authored-by: Genevieve Warren <[email protected]>
Thank you @gewarren! Co-authored-by: Genevieve Warren <[email protected]>
Co-authored-by: Genevieve Warren <[email protected]>
|
@gewarren Snippets 5000 doesn't support .NET 10 yet and I'd rather wait until there are dev container images for preview 1 before I move the snippets to separate code files. Any objections to this approach? |
Yes, I don't think we should keep them inline. You can at least verify that they build locally by placing them in separate code files, and then we can use admin perms to override the Snippets 5000 requirement for merging. cc @cmastr P.S. The reason I'm being a stickler is because I was burnt multiple times in the past by not doing this. |
|
Should you also add ai-assisted metadata to these docs? |
You're no fun, @gewarren. 😝 Okay, I figured out how to build the snippets with the daily build docker container. |
| - Obsoleted Clipboard APIs. | ||
| - New Clipboard related APIs. | ||
|
|
||
| For more information, see [What's new in Windows Forms for .NET 10](https://github.com/dotnet/core/blob/dotnet10p1/release-notes/10.0/preview/preview1/winforms.md). |
There was a problem hiding this comment.
The link should be updated once Andy publishes.
Co-authored-by: Genevieve Warren <[email protected]>
…docs into net10-whats-new
|
|
||
| ## Pruning of framework-provided package references | ||
|
|
||
| Starting in .NET 10, the [NuGet Audit](/nuget/concepts/auditing-packages) feature can now [prune framework-provided package references](https://github.com/NuGet/Home/blob/451c27180d14214bca60483caee57f0dc737b8cf/accepted/2024/prune-package-reference.md) that aren't used by the project. This feature is enabled by default for all `net` target frameworks (for example, `net8.0` and `net10.0`) and .NET Standard 2.0 and greater target frameworks. This change helps to reduce the number of packages that are restored and analyzed during the build process, which can lead to faster build times and reduced disk space usage. It also can lead to a reduction in false positives from NuGet Audit and other dependency-scanning mechanisms. |
There was a problem hiding this comment.
Prune is not specific to audit only. Are you referring to:
It also can lead to a reduction in false positives from NuGet Audit and other dependency-scanning mechanisms.
This read fine to me, since it says NuGet Audit and other dependency scanning mechanisms.
It's available in .NET 10 SDK but we turned it on for all .NET frameworks as well.
There was a problem hiding this comment.
the NuGet Audit feature can now prune framework-provided package references that aren't used by the project
The text presents pruning as an implementation detail of Audit.
Co-authored-by: Rich Lander <[email protected]>
…docs into net10-whats-new
Fixes #44694
Internal previews