You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Interactive rendering required for NotAuthorized component/content to work ... and I'll probably work this in tandem with NotFound content behavioral differences between ASP.NET Core pipeline on the server and WASM on the client.
Account confirmation+PW recovery article for BWA/Identity components UPDATE: I asked multiple times for PU review, and it was never followed up on by PU engineers.
Streaming rendering with Azure hosting Referred to the PU as a support request. I'll re-open and work the issue if they say a remark should be added on hosted (non-Blazor) APIs that might need to flush their response.
Blazor BWA external/social login guidance: This will be based on a Jeremy sample app that will be created within the next week or two. Closed as not planned. We won't have a sample with a specific social auth provider implemented.#30994 (comment)
This received a full overhaul and update to include generalizing the topic with server-side debugging guidance ... BWA (>=8.0) and Blazor Server apps (<8.0). The .NET 8 updates are mostly done. I will open a follow-up issue for a few items, including some trouble that I had with MS Edge browser debugging (can't hit breakpoints).
Blog, PU Issue, PU PRNOTE: Didn't include a fully-working service example that changes the cascading param value with notification or the factory-based approach. Will open an issue later to add these.
Hot reload support for instance fields, properties, and events for .NET on WebAssembly AND Support for symbol servers when debugging .NET on WebAssembly AND Blazor WebAssembly debugging in Firefox
Final updates for standalone issues opened for additional specific work.
Questions for the PU, API doc cross-links, and 8.0 snippet sample cross-links. Questions are tracked by in-text HTML comments that will be checked at (and after) RTM or via the tables/items further down this issue.
Two tasks done and one remains on #30002. It still needs an approach to integrate server- and client-side dynamic culture approaches for BWA (i.e., the Auto render mode scenario).
Fundamentals > Logging: Although the purpose of remarking on "client-side" for several of the features was merely meant to mean from the original text/purpose that the feature also works client-side, the section heading use of "client-side" implies that it might not work server-side, when it actually does. Therefore, I'll probably be dropping "client-side" from headings where the feature/example works for both.
This section of linked issues is assessed for items that didn't make the roadmap but have a bearing on docs. This section will be removed after the last batch for RC2 are assessed. RC1 and RC2 will be assessed after their milestone versions release.
8.0 Post GA
NOTE: Probably best to have the PWA doc reviewed by the PU for any other 8.0 PWA changes.
IN PROGRESS
👷
Waiting on guidance from Halter/Jeremy.
NotAuthorized
component/content to work ... and I'll probably work this in tandem withNotFound
content behavioral differences between ASP.NET Core pipeline on the server and WASM on the client.#31839
[Parameter]
for query string-supplied params.Client
projects of a BWA#31378 (Blazor Security)
#31236
#31268
#31274
#31283
#31286
dotnet/blazor-samples#154
#31341
dotnet/blazor-samples#157
#31364
Asking the PU if they want the BWA template to make layouts more readily consumable with a namespace in the
_Imports
file: dotnet/aspnetcore#52478AddCascadingAuthenticationState
to replace theCascadingAuthenticationState
component in >=8.0ms.date
metadata.dotnet/blazor-samples
to 8.0 release packages.Derived from 8.0 issues/PRs not on the roadmap
🟢 = Ready ✔️ = Done 🛑 = Wait on PU to finish ❌ = No action required
Blog
MapIdentityApi<TUser>()
), Identity Razor components, token auth, etc./register
and/login
(blog post)Requires research in PU issues/PRs
❓❓❓
EditContext.IsValid
API.Live 2
HeadOutlet
componentLive: Host & Deploy WASM
Live: Host & Deploy Server
ServerTimeout
andKeepAliveInterval
dotnet/runtime #80421
dotnet/AspNetCore.Docs #28368
Major updates for full-stack UI by article
Status doesn't include ...
Auto
render mode scenario).Other
<NotFound>
fragment. I need to run thru the docs and confirm that it's out for 8.0+.Derived from the 8.0 roadmap
🟢 = Ready ✔️ = Done 🛑 = Wait on PU to finish ❌ = No action required
Blog
SynchronizationContext
")Requires research in PU issues/PRs
❓❓❓
Moved to .NET 9
Other
Blog
dotnet/blazor-samples/pull/112
#30872dotnet/blazor-samples
sample app updates.Migration
Integration
Blazor Hybrid
Moved to .NET 9
Blog posts for cross-links
Marking "done" on these without addressing the full-stack UI updates because it will be for no earlier than Pre5.
8.0 preview/RC PU issues for analysis
This section of linked issues is assessed for items that didn't make the roadmap but have a bearing on docs. This section will be removed after the last batch for RC2 are assessed. RC1 and RC2 will be assessed after their milestone versions release.
.NET 8 Planning
https://github.com/dotnet/aspnetcore/issues?q=is%3Aopen+is%3Aissue+label%3Aarea-blazor+milestone%3A%22.NET+8+Planning%22
Issues to watch 👀 ...
debounce
/throttling
for events aspnetcore#10522PU roadmap
ASP.NET Core Roadmap for .NET 8 (dotnet/aspnetcore #44984)
The text was updated successfully, but these errors were encountered: