Skip to content

Conversation

@guardrex
Copy link
Collaborator

@guardrex guardrex commented Dec 5, 2025

Addresses #36448


Internal previews

📄 File 🔗 Preview link
aspnetcore/migration/100-to-110.md aspnetcore/migration/100-to-110

@guardrex guardrex self-assigned this Dec 5, 2025
@guardrex guardrex requested a review from ilonatommy December 5, 2025 12:40
@guardrex guardrex changed the title [11.0 P1] Blazor release notes [11.0 P1] Blazor release notes and initial migration guidance Jan 26, 2026
@guardrex
Copy link
Collaborator Author

guardrex commented Jan 26, 2026

@tdykstra @wadepickett ... I needed the Migration infrastructure in place for Blazor migration coverage. I've added it to this PR that adds blazor INCLUDES coverage for the Release notes article.

@guardrex guardrex marked this pull request as ready for review January 26, 2026 14:12
Copy link
Contributor

@tdykstra tdykstra left a comment

Choose a reason for hiding this comment

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


The inline JS event handler that toggles the display of navigation links is no longer present in the `NavMenu` component of the Blazor Web App project template. Apps generated from the project template now use a [collocated JS module](xref:blazor/js-interop/javascript-location#load-a-script-from-an-external-javascript-file-js-collocated-with-a-component) approach to show or hide the navigation bar on the rendered page. The new approach improves [Content Security Policy (CSP) compliance](xref:blazor/security/content-security-policy) because it doesn't require the CSP to include an unsafe hash for the inline JS.

To migrate an existing app to .NET 11, including adopting the new JS module approach for the navigation bar toggler, see <xref:migration/100-to-110>.
Copy link
Contributor

Choose a reason for hiding this comment

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

Should there be an blank line on the end since this is an include?

Copy link
Collaborator Author

@guardrex guardrex Jan 26, 2026

Choose a reason for hiding this comment

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

Yes, there should be a newline at the end of every last content line for every file in GH ... thus a blank line showing at the end of every file.

@guardrex
Copy link
Collaborator Author

Thanks, @tdykstra ... I forgot to place the INCLUDES file in a folder named "includes" 💥.

@guardrex
Copy link
Collaborator Author

The warnings that will appear here are the standard filename warnings. IMO, they should get rid of those, but we have a lot to update to address all of them, including the underscores in many folders around the repo (I have an issue to work on that at some point).

Copy link
Contributor

@wadepickett wadepickett left a comment

Choose a reason for hiding this comment

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

Looks great. Approved.

See my question/suggestion around what I think might be a typo for .NET 10 vs .NET 11.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

11.0 .NET 11

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants