From 835946b7323228526f310e0887ed66655667d56e Mon Sep 17 00:00:00 2001 From: Vladimir Pecanac Date: Thu, 13 Aug 2026 11:27:36 +0200 Subject: [PATCH] Retarget BlazorSections sample to net10.0, add README with render mode note --- .../BlazorSections/BlazorWasmApp/BlazorWasmApp.csproj | 6 +++--- blazor-features/BlazorSections/README.md | 9 +++++++++ 2 files changed, 12 insertions(+), 3 deletions(-) create mode 100644 blazor-features/BlazorSections/README.md diff --git a/blazor-features/BlazorSections/BlazorWasmApp/BlazorWasmApp.csproj b/blazor-features/BlazorSections/BlazorWasmApp/BlazorWasmApp.csproj index a7dbcaa5bd..82d74552ed 100644 --- a/blazor-features/BlazorSections/BlazorWasmApp/BlazorWasmApp.csproj +++ b/blazor-features/BlazorSections/BlazorWasmApp/BlazorWasmApp.csproj @@ -1,14 +1,14 @@ - net8.0 + net10.0 enable enable - - + + diff --git a/blazor-features/BlazorSections/README.md b/blazor-features/BlazorSections/README.md new file mode 100644 index 0000000000..f12c328374 --- /dev/null +++ b/blazor-features/BlazorSections/README.md @@ -0,0 +1,9 @@ +# Blazor Sections + +Sample project for the "Blazor Sections: SectionOutlet and SectionContent" article. + +Standard Blazor WebAssembly Standalone App template (`net10.0`). The app has no server-rendering +component, so it runs entirely in the browser under `InteractiveWebAssembly`-equivalent +client-side rendering — there is only one render mode in play, which is why `SectionOutlet` and +`SectionContent` resolve without the layout/page render-mode mismatch the article's "Interactive +Render Modes" section describes for Blazor Web Apps.