Fix ManageLayout.razor uses wrong layout namespace for WASM/Auto Global Blazor projects#3764
Open
haileymck wants to merge 1 commit into
Open
Fix ManageLayout.razor uses wrong layout namespace for WASM/Auto Global Blazor projects#3764haileymck wants to merge 1 commit into
haileymck wants to merge 1 commit into
Conversation
…al Blazor projects In Blazor WASM/Auto (Global interactivity) projects, MainLayout.razor lives in the client project (e.g. BlazorApp1.Client), not the server project's Components/Layout/ folder. The scaffolder was always generating: @layout BlazorApp1.Components.Layout.MainLayout which causes CS0234 because the Layout namespace doesn't exist under BlazorApp1.Components in WASM/Auto Global projects. Fix: detect whether Components/Layout/MainLayout.razor exists in the server project directory. If it does (Blazor Server), use the .Components.Layout namespace. If not (WASM/Auto Global), use .Client.Layout instead. Fixes both the dotnet-scaffold (ValidateIdentityStep) and the VS scaffolder (BlazorIdentityGenerator) code paths. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 https://devdiv.visualstudio.com/DevDiv/_workitems/edit/2993217
In Blazor WASM/Auto (Global interactivity) projects, MainLayout.razor lives in the client project (e.g. BlazorApp1.Client), not the server project's Components/Layout/ folder. The scaffolder was always generating:
@layout BlazorApp1.Components.Layout.MainLayout
which causes CS0234 because the Layout namespace doesn't exist under BlazorApp1.Components in WASM/Auto Global projects.
Fix: detect whether Components/Layout/MainLayout.razor exists in the server project directory. If it does (Blazor Server), use the .Components.Layout namespace. If not (WASM/Auto Global), use .Client.Layout instead.
Fixes both the dotnet-scaffold (ValidateIdentityStep) and the VS scaffolder (BlazorIdentityGenerator) code paths.