Blazor 6.0 content tracking issue

[guardrex]

6.0 Broken down by PU assignee

Assignment currently undetermined

• Blazor WASM native dependencies support | Live | Edit | I hit a little 🐛 while working on this, but it seems to be some kind of Emscripten problem with my ancient 10-year-old PC 🙈.
• WebAssembly AoT Compilation with runtime relinking guidance | AOT Live | Runtime Relinking Live | Edit | Reviewed (but not approved) by DR.
• Persist prerendering state | Live 1 | Edit 1 | Live (Tag Helper) | Edit 2 | Approved by DR.
• NRTs and compiler null-state checks | Live | Edit | There will be a final pass to update inline doc examples after 6.0 GA and hopefully 🤞 before the 🎁 holiday break ⛄.
• Blazor 6.0 migration content | 23607 | Live | Edit | PR approved by Artak.

Hao (and perhaps Barry)

• Duende for Identity Server/AAD | 23047 | See PR because this touched several spots.

Safia

• Add support for error boundaries in Blazor | Live | Edit
• Improve SVG support in Blazor | Live | Edit

Tanay

• Blazor Server: Support byte-array transfer in JS Interop | Call JS Live | Call .NET Live | Call JS Edit | Call .NET Edit
• Blazor Server: Remove size limitations imposed by SignalR message size | 23739 & 23740

Mackinnon

• Query string enhancements | Live (+6 sub-sections) | Edit
• Support binding to select multiple, getting/setting the selection as an array | Live (Binding) (+next section) | Live (Forms) | Edit (Binding) | Edit (Forms)
• Update Blazor head components | Live | Edit
• Generate Angular and React components using Blazor | Live | Edit

Steve

• Render components from JS | Live | Edit
• Blazor custom elements | Live | Edit
• Infer component generic types from ancestor components | Live | Edit
• Dynamically rendered components (DynamicComponent) | Live | Edit
• Improved Blazor accessibility: FocusOnNavigate | Live | Edit
• Support custom event args in Blazor | Live | Edit

Pranav

• Required parameters to blazor components | Live (scroll to end of section) | Edit

Javier

• Collocate JS files with pages, views, and components | include | Edit | The INCLUDE is displayed in the Blazor JS interop overview topic and the Blazor RCL topic. **More work needed to surface for RP/MVC. I've noted this in my tracking for more work, which I'll reach this week (Wednesday, 10/27). For more info on this work, see the PR at 23327.
• JavaScript initializers | include | Edit | Include displayed in the Blazor Fundamentals Startup topic and the JS interop overview.
• .NET to JS Streaming Interop | Live | Edit | This and the next entry are in the Call JS from .NET topic SxS in two sections. This was done because "call" in this context is a bit muddy. Who is "calling" who given that these sections are focused on "streaming," not "calling," per se. You might decide that we need to move one or the other over to the Call .NET from JS topic. 👂
• Stream from JavaScript to .NET | Live | Edit | This and the previous entry are in the Call JS from .NET topic SxS in two sections. You might decide that we need to move one or the other over to the Call .NET from JS topic. 👂
• Allow generic type constraints | Live | Edit
• WASM deployment layout topic | Live | Edit | ⚔️ Sir blowdart 🎯 is ok with note content on bypassing DLL-network restrictions.

On HOLD or Coming Soon

• Customize Blazor WASM packaging 🛑 HOLD for PU/blog-supplied content. This may refer to a remark on the JS collocate/initializers PR.
• Dynamically added root components 🛑 HOLD for PU-supplied content.
• Blazor hybrid desktop apps (.NET MAUI) 🛑 HOLD for PU coordination offline.

Dropped or not required

• PageX and PageY No docs required. This is covered by API docs.
• Blazor Server: More control over circuits lifetime CUT by PU.
• Expose location changing event for NavigationManager CUT by PU.
• Drag & Drop CUT by PU.
• Input ElementReference exposed on relevant components No docs required.
• Specify null for Action/RenderFragment component params No docs required.
• Pause and resume Blazor applications CUT by PU.
• Blazor Server: Specific components for dealing with large binary data (files and media) CUT by PU.
• Blazor Server: Specific component for dealing with large amounts of text data (InputTextArea) CUT by PU.
• Launch DebugProxy from blazorwasm debug type in VS Code No docs required.

6.0

Status	Docs Issue	Docs PR	Item	Notes
✔️	23522	23530	Blazor WASM native dependencies support	Blog Post. Hit a 🐛 on the PR, but it was probably just a point-in-time thing with RC2. I'll check the scenario at GA.
✔️	23402	23411 Live Edit	WASM deployment layout topic	⚔️ Sir blowdart 🎯 and I discussed the general bypass-DLL-network-restrictions-at-your-own-risk NOTE offline, and the DRAFT content should suffice until final review+approval prior to GA.
✔️	23294	23313 Live Edit	Render components from JS	Blog Post
✔️	23295	23314 Live Edit	Blazor custom elements	Blog Post
✔️	23297	23315 Live Edit	Generate Angular and React components using Blazor	Blog Post
✔️	23298	❌	PageX and PageY	No docs required. This is covered by API docs. Blog Post
✔️	23299	23327 include Edit See NOTE 👉	Collocate JS files with pages, views, and components	Blog Post PU PR; NOTE: Include displayed in Blazor JS interop overview topic and Blazor RCL topic. More work needed to surface for RP/MVC. See the docs PR for remarks, and I've noted this below in Non-Blazor (but related) features area for more work.
✔️	23300	23331 include Edit See NOTE 👉	JavaScript initializers	Blog Post PU PR; NOTE: Include displayed in Blazor Fundamentals Startup topic and JS interop overview.
❓	—	—	Customize Blazor WASM packaging	I think this might be a duplicate entry for JS initializers and deployment layouts.
✔️	23039	23046 Live Edit See NOTE 👉	.NET to JS Streaming Interop	PU PR; NOTE: This and the next entry are in the Call JS from .NET topic SxS in two sections. This was done because "call" in this context is a bit muddy. Who is "calling" who given that these sections are focused on "streaming," not "calling," per se. You might decide that we need to move one or the other over to the Call .NET from JS topic. 👂
✔️	23013	23014 Live Edit See NOTE 👉	Stream from JavaScript to .NET	Blog Post PU PR; NOTE: This and the previous entry are in the Call JS from .NET topic SxS in two sections. This was done because "call" in this context is a bit muddy. Who is "calling" who given that these sections are focused on "streaming," not "calling," per se. You might decide that we need to move one or the other over to the Call .NET from JS topic. 👂
✔️	22355	23047 See PR because this touched several spots. Already signed off by Barry and Hao.	Duende for Identity Server/AAD	PU Issue Applies to the entire doc set (Blazor + non-Blazor). See: 32881
✔️	22863	23033 Live Edit PR approved by Tanay.	Using Long Polling for Blazor Server	PU Issue PU PR
✔️	22689	23000 Live (+6 sub-sections) Edit PR approved by Mackinnon.	Query string enhancements	PU Issue PU PR 1 PU Design for building PU PR 2
🛑 HOLD until RC2 release for PU-supplied content	22690	23032†	Dynamically added root components	PU Issue PU PR †Had to close due to need for PU input. Check back with SS after RC2 releases.
✔️	22440	23065 Live Edit Reviewed (but not approved) by Dan.	Hot reload for Blazor	Feature Still Under Development PU Issue Search PU Issue Blog Post 3 Blog Post 5
✔️	22442	23065 AOT Live RR Live Edit Reviewed (but not approved) by Dan.	WebAssembly AoT Compilation with runtime relinking guidance	PU Issue Blog Post 4 Blog Post 5
🛑 HOLD for PU coordination offline	22441	—	Blazor hybrid desktop apps (.NET MAUI)	PU Issue Blog Post 3 Blog Post 4
✔️	22443	22683* See NOTE 👉	Launch DebugProxy from blazorwasm debug type in VS Code	PU Issue; NOTE: *Closed as no docs required per Capt. Safia 🎖️.
✔️	21769	21846 Live Edit	Infer component generic types from ancestor components	PU Issue PU PR Blog Post 2
✔️	22444	❌	Blazor Server: More control over circuits lifetime	CUT by PU PU Issue
✔️	22444	22718 Call JS Live Call .NET Live Call JS Edit Call .NET Edit PR approved by Tanay.	Blazor Server: Support byte-array transfer in JS Interop	PU Issue PU PR Announcement
✔️	22444	23031 IIRC, approved by Tanay in issue discussion.	Blazor Server: Remove size limitations imposed by SignalR message size	PU Issue
✔️	22444	❌	Blazor Server: Specific components for dealing with large binary data (files and media)	CUT by PU PU Issue
✔️	22444	❌	Blazor Server: Specific component for dealing with large amounts of text data (InputTextArea)	CUT by PU PU Issue
✔️	21763	21755 Live Edit	Support custom event args in Blazor	PU Issue Blog Post 2
✔️	22445	22696 Live (scroll to end of section) Edit	Required parameters to blazor components	PU Issue PU PR Blog Post 6
✔️	17351	22697 Live Edit	Allow generic type constraints	PU Issue Blog Post 4
✔️	22446	22688 Live Edit PR approved by Safia.	Add support for error boundaries in Blazor	PU Issue Blog Post 4
✔️	22447	❌	Pause and resume Blazor applications	CUT by PU PU Issue
✔️	22448	22770 Live (Binding) (+next section) Live (Forms) Edit (Binding) Edit (Forms) PR approved by Mackinnon.	Support binding to select multiple, getting/setting the selection as an array	PU Issue PU PR
✔️	22449	❌	Expose location changing event for NavigationManager	CUT by PU PU Issue
✔️	22005	22984 Live Edit PR approved by Dave Brock.	Dynamically rendered components (DynamicComponent)	PU Issue Blog Post 1 PU PR DB Blog Post
✔️	20319	22929 22931 Live Edit PR approved by Mackinnon.	Update Blazor head components.	PU Issue PU PR 1 PU PR 2
✔️	—	23364	Prerendering and integration topic updates	These updates include control of head content for the scenarios described in the topic (i.e., the third step of updates on the Update Blazor head components 🤠 Texas Three-step™ 🕺💃 called out on those issues/PRs ☝️).
✔️	22450	22717 Live Edit PR approved by Safia.	Improve SVG support in Blazor	PU I1 PU I2 PU PR Blog Post 5
✔️	21992	❌	Drag & Drop	CUT by PU PU Issue
✔️	21771	22732 (First added PR) 23621 (Update PR) Live 1 Edit 1 Live (Tag Helper) Edit 2 PR approved by Dan.	Persist prerendering state	Blog Post 2
✔️	22451	❌	Input ElementReference exposed on relevant components	No docs required. Blog Post 1
✔️	❌	❌	Specify null for Action/RenderFragment component params	No docs required. Blog Post 5
✔️	23603	23607 Live Edit	Blazor 6.0 migration content	Approved by Artak.
✔️	22734	22735 Live Edit	Improved Blazor accessibility: FocusOnNavigate	Blog Post 6
✔️	23392	23504 Live Edit	NRTs and compiler null-state checks	I've decided to notify readers via the Project Structure topic, where the Blazor templates are discussed. The updates to doc examples will occur transparently because C# language features are beyond the scope of Blazor docs ... we just want the doc examples updated to embrace NRTs and null-state checks. The code example work will be tracked by this issue (6.0 GA table 👇). The PR for to resolve this item is just to call it out in the text.

RC1

• Update the transient dependency example for 6.0 #23482 Resolved by Transient dependency example #23490 and Transient dependency example (2) #23491.
• Minimal API updates: Sweep for Startup.cs, Startup.ConfigureServices, Startup.Configure, Program.Main (and Main methods) in Blazor guidance. Blazor minimal API updates #23483
• Check on the project structure topic vis-a-vis Additional content for Blazor Server _Layout.cshtml: https://devblogs.microsoft.com/aspnet/asp-net-core-updates-in-net-6-rc-1/#blazor-templates-updated-to-set-page-title Checked ... no updates needed.
• Remove the new state preservation feature language per Blazor preserve state during prerendering #22732: Search on "6.0" in the Blazor node. Blazor preserve state and RC updates #23308
• Snippet sample apps and EFCore-Server sample app to RC1. Blazor snippet and EFCore-Server sample updates #23343 — Blazor snippet and EFCore-Server sample updates #23343
• SignalR-Blazor tutorial sample apps update to RC1. Blazor tutorials updates #23397
• Todo List tutorial update to RC1. Blazor tutorials updates #23397
• Remove PreferExactMatches from Blazor samples at 6.0 #20951 — Confirm that PreferExactMatches INCLUDES content/versioning is good and that it's removed from sample apps. Checked ... no updates needed.

RC2

• Snippet sample apps and EFCore-Server sample app to RC2. Updates are on Blazor snippet sample NRT updates #23518.
• SignalR-Blazor tutorial sample apps update to RC2. Updates are on Blazor snippet sample NRT updates #23518.
• Check on API renames 👉 https://devblogs.microsoft.com/aspnet/asp-net-core-updates-in-net-6-rc-2/#breaking-changes-apis-renames. Checked ... no updates needed.

PU roadmap, announcements, and blog posts

• ASP.NET Core Roadmap for .NET 6 aspnetcore#27883
• https://github.com/aspnet/Announcements/issues?q=is%3Aissue+label%3A6.0.0
• https://devblogs.microsoft.com/aspnet/asp-net-core-updates-in-net-6-preview-1/
• https://devblogs.microsoft.com/aspnet/asp-net-core-updates-in-net-6-preview-2/
• https://devblogs.microsoft.com/aspnet/asp-net-core-updates-in-net-6-preview-3/
• https://devblogs.microsoft.com/aspnet/asp-net-core-updates-in-net-6-preview-4/
• https://devblogs.microsoft.com/aspnet/asp-net-core-updates-in-net-6-preview-5/
• https://devblogs.microsoft.com/aspnet/asp-net-core-updates-in-net-6-preview-6/
• https://devblogs.microsoft.com/aspnet/asp-net-core-updates-in-net-6-preview-7/
• https://devblogs.microsoft.com/aspnet/asp-net-core-updates-in-net-6-rc-1/
• https://devblogs.microsoft.com/aspnet/asp-net-core-updates-in-net-6-rc-2/
• https://devblogs.microsoft.com/dotnet/announcing-asp-net-core-in-net-6/

6.0 Post GA

Status	Docs Issue	Docs PR	Subject
✔️			For #23668, update the native dep cross-link the Hosting Model topic. Done! #23668
✔️			After the Native Deps PR (dotnet/AspNetCore.Docs #23668) merges and goes live: Open a follow-up issue on HOLD to convert preview language for SkiaSharp when SkiaSharp reaches GA. Done! #23904
✔️	#23825	#23831	Hot Reload guidance move follow-up cross-link update for What's New topic.
Tracked for final work 🛠️ by 24491	24491	#23842	Review and update What's New content for Blazor, which will be located here after publication. Original content. The last three items require content and removal of HTML comment markers.
	#23064		Move new 6.0 example code block snippets into the Blazor snippet sample apps (include NRT work on these examples).
✔️	#23063	#23842	Add 6.0 Blazor API doc cross-links
✔️	#21897	#23811	Snippet sample apps and EFCore-Blazor Server final updates to release bits.
💥	#21899		Blazor-SignalR tutorial confirm/update VS UI guidance (Windows and macOS) Waiting on Aquent Mac
✔️	#21898	#23365	Policy hashes. I think this is resolved by #23365. If not, the readership will sharpen their beaks and claws for me! 🦅😨
✔️		#23365	Merge this PR
✔️			Check/update the API doc cross-links in the Blazor Hub endpoint route configuration section of Fundamentals > SignalR topic. Content OK 👍 ... no updates needed.
✔️		#23813	Cross-link the Minimal API doc in the main doc set into the Blazor docs.
✔️		#23813	GA Revert "*preview release*" language for 6.0 from multiple topics where it appears. Also search and destroy for anything mentioning "6.0 preview".
✔️		#23813	Update doc dates to GA date
✔️		#23813	Update VS 2019 (the date) to VS 2022.
✔️	#23620	#23504	NRT and compiler null-state static analysis updates. Snippet sample apps are done, sans one EF Core-Blazor Server NRT 😈. Guidance appears at Nullable reference types (NRTs) and .NET compiler null-state static analysis. The remaining work to address inline doc examples hopefully will occur before the 🎁 holiday vacation ⛄ and no later than 22Q1. The issue is tracked by the Blazor.Docs project, so it doesn't block closing out this 6.0 tracking issue.
✔️	#23864		Open a followup issue for "* In Visual Studio 2022 GA (17.0), Hot Reload is only supported when running without the debugger." when VS can handle it. aspnetcore/test/hot-reload.md Done! ... and marked on HOLD on the Blazor.Docs project so that it won't get lost.
💥			PROBLEM ATM: My iMac is so old that it can't take macOS 10.14. Therefore, it can't take VS for Mac 2022. Therefore, I can't update docs for UI changes. I'm waiting on Aquent to send me a late-model Mac. This entry will be addressed as soon as that Mac arrives. 🚚 VS for Mac 2022 is still in preview for 6.0. Search for "preview" to isolate and update the guidance. It's probably best to keep the text in the docs where it cross-links to content on how to use the Preview channel and just comment it out. This is going to be recurring guidance each time VS for Mac goes into preview for an upcoming release, and it will be simpler to keep the guidance there in an unrendered state between releases. Note that this update includes Blazor node docs and the Blazor-SignalR tutorial.

Non-Blazor (but related) features

Status	Docs Issue	Docs PR	Subject	Source
✔️	23120	23389 Live Edit	RP/MVC CSS isolation	PU Issue PU PR Blog Post 2
✔️	❌	❌	Single-file publishing	CUT by PU PU Issue

[fiyazbinhasan]

Hey @guardrex! I can see some cool stuff coming in Blazor 6.0 docs. Do you need an extra hand? Let me know how you are planning to resolve these. Thanks 😺

[guardrex]

Yes, @fiyazbinhasan ... that would be great to have help with the updates. They're on hold right at the moment for two reasons ...

• We've been burned a few times in the past documenting upcoming release features, particularly the large features (new topics usually) during preview due to engineering churn. We document something well ... the engineers take feedback and think things over and then decide to change the bits ... the new docs are then stale and must be revisited and updated. If the changes are small, no problem. Sometimes tho, the changes are LARGE. It's time-consuming and costly 💰 when this happens, so we generally hold off until RC1 (or close to RC1) before documenting most upcoming release features. We're still a couple of months away from RC1. Historically, there's been plenty of time between RC1 and GA to get everything documented, too. There's usually at least two full months, often three.
• I'm not aware yet on a few of these if the PU wants to provide content, possibly code, for the doc updates. For most of these, text and code is readily available from the PU issue/PR and DR's preview blog posts. For most of these, the PU will be quite happy not to have to provide anything ... indeed, the less they hear about docs the better 🙈😆.

When the time comes to work on these, the plan is to use the individual tracking issues (first column ☝️) to decide where the content will live (e.g., section of a topic or new topic, titling, metadata, etc.) and what sort of example code would be good. To speed up working example code in, what we'll probably do is place code directly into the topics and then I'll circle around after GA and move that code into the snippet sample apps.

I'll ping u back here when I have more info on the plan for these.