Blazor support to an ASP.NET Core app (Part 2)#30799
Conversation
|
@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. |
|
@danroth27 ... Ready for another look.
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. |
|
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. |
Co-authored-by: Daniel Roth <daroth@microsoft.com>
danroth27
left a comment
There was a problem hiding this comment.
Looks good! Just a few nits.
Co-authored-by: Daniel Roth <daroth@microsoft.com>
Fixes #30471
Internal previews