Skip to content

Blazor support to an ASP.NET Core app (Part 2)#30799

Merged
guardrex merged 8 commits intomainfrom
guardrex/blazor-integration
Oct 24, 2023
Merged

Blazor support to an ASP.NET Core app (Part 2)#30799
guardrex merged 8 commits intomainfrom
guardrex/blazor-integration

Conversation

@guardrex
Copy link
Copy Markdown
Collaborator

@guardrex guardrex commented Oct 20, 2023

@guardrex
Copy link
Copy Markdown
Collaborator Author

@danroth27 ... I think it best tho to pick back up with this on Monday. If I could wrap it up quickly ... 15 minutes ... I'd do so. This will take a bit more time tho, plus I'd like to exercise 🦖 The Rex Gambit™ 🦖 on the first two sections with a bit more spit-'n-polish, remarks, and cross-links. This would all be better served if I dig in on Monday morning.

@guardrex guardrex self-assigned this Oct 20, 2023
@guardrex
Copy link
Copy Markdown
Collaborator Author

guardrex commented Oct 23, 2023

@danroth27 ... Ready for another look.

Note that in order to change section three to rely on section one (and not exist as a completely independent set of steps), it also needs to rely on section 2 because it seems ... correct me if I'm wrong ... server interactive rendering is needed for Auto render mode to work.

... and the section name must change (swapping "and" for "or") to Enable interactive Auto and WebAssembly rendering.

The alternative is for us to split section three into two sections ...

* Enable interactive WebAssembly rendering (i.e., only WASM rendering)
* Enable interactive Auto rendering, which would have the dev perform all three preceding sections (static, server, and WASM), and then use the donor BWA for the bits.

UPDATE (10/24): Let me try something on the next commit to address this problem. It seems to me now that section two can be optional for section three depending on if the dev wants Auto or only interactive WASM rendering.

@guardrex
Copy link
Copy Markdown
Collaborator Author

guardrex commented Oct 24, 2023

I made updates that I think address the Auto-WASM problem in the third section. I prompt the dev to make a decision on adopting Auto or WASM rendering, then I guide them in the following steps based on their decision. This should eliminate my earlier concern.

... and I'll place all of the API doc cross-links later. That system they set up for providing the links during preview still isn't working well. Many of the latest RC2 API links aren't present yet for use. It's better if I just circle around post-release and place them at that time.

Comment thread aspnetcore/blazor/components/integration.md Outdated
Co-authored-by: Daniel Roth <daroth@microsoft.com>
Comment thread aspnetcore/blazor/components/integration.md Outdated
Comment thread aspnetcore/blazor/components/integration.md Outdated
Comment thread aspnetcore/blazor/components/integration.md Outdated
Comment thread aspnetcore/blazor/components/integration.md Outdated
Comment thread aspnetcore/blazor/components/integration.md Outdated
Copy link
Copy Markdown
Member

@danroth27 danroth27 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! Just a few nits.

guardrex and others added 2 commits October 24, 2023 17:03
Co-authored-by: Daniel Roth <daroth@microsoft.com>
@guardrex guardrex merged commit 3708fb5 into main Oct 24, 2023
@guardrex guardrex deleted the guardrex/blazor-integration branch October 24, 2023 21:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Document how to add Auto component rendering to a Blazor Server app in .NET 8

2 participants