ASP.NET Core Roadmap for .NET 10

[mkArtakMSFT]

Discussion thread on the ASP.NET Core Roadmap for .NET 10

[joegoldman2]

I would like to see some progress around Observability.

Native instrumentation support:

• [.NET 9.0] Native Trace Instrumentation Support for ASP.NET Core as per OTel specification #52439

Remove some log scopes that no longer make sense with OpenTelemetry and span attributes:

• Ability to disable ConnectionId and RequestId + RequestPath scopes #31028
• Remove default logging scope from ASP.NET Core #44873

Ability to add attributes to the root activity to facilitate Head Sampling:

• Allow additional Tags for activity creation #50488

[boukenka]

I would like to see some progress for the Consider shipping ObjectGraphDataAnnotationsValidator / ValidateComplexTypeAttribute issue, which has been open since December 14, 2020 (47 up votes so far)

[hez2010]

I would like to see blazor being fully trimming compatible in .NET 10: #49409
As it's the prerequisites of building blazor client apps with NativeAOT-LLVM.

We have experimented NativeAOT-LLVM with Avalonia wasm apps and the performance is way faster than mono-aot, also the binary size is also smaller than mono-aot by a lot. Here is an example of a NativeAOT-LLVM compiled Avalonia app: sizoscopeX, you can test this app with sample-data.zip by selecting both the two files in the archive in the Open dialog to see how fast it is.

I expect blazor to have even better experience, as blazor doesn't use external libraries (like libSkia) for rendering so that the binary size should be a lot smaller than Avalonia.

[BrunoBlanes]

I'd also like to see MVC get support for trimming #41767, at least for controllers, since minimal APIs isn't a fit for everyone.

[CrahunGit]

I would like to see Signalr from blazor server working with authentication (cookies or jwt). It can share the signalr connection used by render updates.

[rogihee]

My personal wishlist:

1. Support for multiple Blazor Web apps per server project #52216 (it was on the Roadmap for 8 and 9 but not yet on 10):
2. Avoid completely replacing the DOM when Blazor components are re-rendered after prerendering #42561 (this hurts a lot when toggling between pre-rendering and rendering)
3. JSInitializer.importInitializersAsync doesn't respect initializerArguments #44586 (makes library initializers not work)
4. Razor compiler should fail if a component has an attribute that is not a parameter and component is "pure" (no AdditionalAttributes parameter catch-all defined). This causes the most runtime regressions / errors that are hard to detect when migrating between versions of external component libraries.
5. Routing that supports multiple languages (ideally: a source generator that generates unique routes that can be referenced in code as well, independent of language, with support for resx-based slugs)

[HectorOrtizTorresInnomotics]

I would like to have more functionality in QuickGrid for example the ability to implement conditional formatting (by rows or by columns) without losing PropertyColumn filtering and sorting functionality. TemplateColumn kind of allows to do the conditional formatting but you lose the Filtering and Sorting Functionalities. Can we have all the PropertyColumn goods in the TemplateColumn or the ability to have ChildContent in the PropertyColumn.