Blazor project templates use inconsistent Bootstrap folder structure across VS2022 (Windows) and .NET CLI (Mac/Linux)

[ycfay]

Description
When creating a new Blazor Server or Blazor WebAssembly project, the Bootstrap library is restored into different folder structures depending on whether the project was created in Visual Studio 2022 on Windows or using the .NET CLI on Mac/Linux.

This leads to missing styles (404 bootstrap.min.css) when the same project is opened on another platform, because the default _Layout.cshtml (or index.html) hardcodes a specific path.

Steps to reproduce
On Windows with VS2022:
Create a new Blazor Server App (using default template).
Observe that Bootstrap is placed in:
wwwroot/lib/bootstrap/dist/css/bootstrap.min.css

On Mac (or Linux) using CLI:
Run:
dotnet new blazorserver -o RazorDemo
cd RazorDemo
Observe that Bootstrap is placed in:
wwwroot/lib/bootstrap/css/bootstrap.min.css
Copy the project between Windows and Mac.
Run the app.
Notice that styles are missing due to path mismatch.

Expected behavior
Both templates should use the same folder structure for Bootstrap (e.g., consistently wwwroot/lib/bootstrap/dist/css/).
This will prevent cross-platform inconsistencies and missing styles.

Actual behavior
VS2022 (Windows) → dist/css/
.NET CLI (Mac/Linux) → css/
Causes missing styles when the project is shared or moved across platforms.

Environment
.NET SDK: 9.0.303 (Mac), 9.0.7 runtime installed
Visual Studio 2022 (Windows)
macOS 15 / Windows 11

Additional context
This looks like a project template / LibMan configuration mismatch.
It would help if the templates were unified or _Layout.cshtml used a consistent reference.

[javiercn]

@ycfay thanks for contacting us.

Create a new Blazor Server App (using default template).

Can you be more specific? are you talking about a Blazor Web App with Interactive Server components or the old Blazor Server template?

[dotnet-policy-service]

Hi @@ycfay. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[dotnet-policy-service]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

See our Issue Management Policies for more information.