Blazor migration guidance #23603
Description
@Rick-Anderson @serpent5 ... Looks like the big updates PR for 6.0 migration just merged. There's nothing else open today for the topic, correct? I'd like to add a few Blazor bits in a short† section while there aren't pending updates on another PR. It's Friday 🎉🍻 ... not a good weekday for conjuring a Merge Conflict Boss 👹😄.
†short: This will be the first Blazor release where we don't cover every app migration change for complete 6.0 feature adoption. That was a giant pain point back for 5.0, where it took about six trips into the migration topic to get every little bit in place. This time, we're just going to cover the minimal requirement to migrate/compile/run for a 5.0-to-6.0 app move. If a dev wants every new 6.0 feature in one shot, I'll advise in the section that we recommend generating a new project from one of the 6.0 templates and then migrating their code and components to the new 6.0 app.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
- ID: 5bec61f9-7298-170d-5e12-abb27cde584e
- Version Independent ID: 27a43e3f-149d-9058-f937-0eda1d6dd4f2
- Content: Migrate from ASP.NET Core 5.0 to 6.0
- Content Source: aspnetcore/migration/50-to-60.md
- Product: aspnet-core
- Technology: aspnetcore-migration
- GitHub Login: @Rick-Anderson
- Microsoft Alias: riande
Metadata
Metadata
Assignees
Type
Projects
Status