Add a migration scenario for Blazor #34011
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #34007
cc: @Rick-Anderson ... I'll get any remaining Blazor migration items on here as they come to light in my discussion with Mackinnon.
Mackinnon ... I think outside of the ASP.NET Core-wide changes (TFM, packages, Map Static Assets routing endpoint conventions) that simplified authentication state serialization is the only migration item ... an optional feature but probably a good idea for devs to adopt. Can you think of any others?
BTW ... Although the project templates and Blazor sample apps for 9.0 adopt the latest Bootstrap version, that's a dev task in their own apps that might require other Bootstrap-specific implementation changes, not a MS product, and not on the same release cadence as .NET. Therefore, I'm not placing guidance on updating for latest Bootstrap.