Replies: 7 comments 7 replies
-
|
Blazor Improve:
|
Beta Was this translation helpful? Give feedback.
-
|
I would like to see some progress around Observability. Native instrumentation support: Remove some log scopes that no longer make sense with OpenTelemetry and span attributes: |
Beta Was this translation helpful? Give feedback.
-
|
Multithreading for Blazor WASM sounds cool, but an easy way to call web-workers, coded with .NET, would also be really nice. |
Beta Was this translation helpful? Give feedback.
-
|
First of all, thank you for the continued work on Blazor WebAssembly and .NET Native AOT. Blazor WASM has reached an impressive level of performance, and AOT has huge potential for real production applications. However, in real-world production projects, enabling AOT together with trimming is still very difficult and fragile, especially when reflection, System.Text.Json, and third-party component libraries are involved. Below are some concrete pain points and suggestions based on real production usage. Reflection remains a major blockerMany real Blazor apps rely on:
With AOT + trimming enabled, applications often build successfully but fail at runtime with errors such as:
Today, developers must rely on:
This approach is difficult to maintain and discourages using AOT in production. Suggested improvements:
System.Text.Json is not AOT-friendly by default
In medium to large applications:
Common issues only appear at runtime even though the build succeeds. Suggested improvements:
AOT + trimming should fail at build timeCurrently:
This is risky for production systems. Suggested improvements:
Trimming documentation and third-party librariesDocumentation around trimming safety needs significant improvement, especially when using third-party Blazor libraries. Libraries such as Syncfusion and MudBlazor are widely used in production, yet:
Suggested improvements:
Trimming guidance is unclearCurrent guidance often suggests:
This leads to trial-and-error rather than confidence. Suggested improvements:
SummaryBlazor WebAssembly AOT is extremely promising, but today:
Improving reflection handling, JSON source generation defaults, build-time diagnostics, and trimming documentation (especially for libraries like Syncfusion and MudBlazor) would make Blazor WebAssembly AOT far more reliable and production-ready. Thank you again for your continued work on Blazor and .NET. |
Beta Was this translation helpful? Give feedback.
-
|
My top 3, looking for upvotes if applicable:
|
Beta Was this translation helpful? Give feedback.
-
|
My top 3 niche requests as a MudBlazor dev |
Beta Was this translation helpful? Give feedback.
-
|
I'm very grateful for the current HTTP/3 via QUIC implementation used by WebTransport. Is it technically possible to take HTTP/3 and WebTransport out of beta and support datagrams in WebTransport? If so, will there be time? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Discussion thread on the ASP.NET Core Roadmap for .NET 11
Beta Was this translation helpful? Give feedback.
All reactions