Skip to content

Merge to Live #37052

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
wadepickett merged 1 commit into from
Apr 23, 2026
Merged

Merge to Live #37052

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion aspnetcore/razor-pages/ui-class.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ For information on how to integrate npm and webpack into the build process for a

# [Visual Studio](#tab/visual-studio)

* From Visual Studio select **Create a new project**.
* From Visual Studio's **Start Window**, select **Create a new project**. Alternatively, select the **File** > **New** > **Project/Solution**.
* Select **Razor Class Library** > **Next**.
* Name the library (for example, "RazorClassLib"), > **Create**. To avoid a file name collision with the generated view library, ensure the library name doesn't end in `.Views`.
* Select **Support pages and views** if you need the library to contain pages and/or views. By default, only Razor components are supported. Select **Create**.
Expand Down
6 changes: 3 additions & 3 deletions aspnetcore/razor-pages/ui-class/includes/ui-class6.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ For information on how to integrate npm and webpack into the build process for a

# [Visual Studio](#tab/visual-studio)

* From Visual Studio select **Create new a new project**.
* From Visual Studio's **Start Window**, select **Create a new project**. Alternatively, select **File** > **New** > **Project/Solution**.
* Select **Razor Class Library** > **Next**.
* Name the library (for example, "RazorClassLib"), > **Create**. To avoid a file name collision with the generated view library, ensure the library name doesn't end in `.Views`.
* Select **Support pages and views** if you need to support views. By default, only Razor Pages are supported. Select **Create**.
Expand Down Expand Up @@ -175,7 +175,7 @@ Razor views, pages, controllers, page models, [Razor components](xref:blazor/com

# [Visual Studio](#tab/visual-studio)

* From Visual Studio select **Create a new project**.
* From Visual Studio's **Start Window**, select **Create a new project**. Alternatively, select the **File** > **New** > **Project/Solution**.
* Select **Razor Class Library** > **Next**.
* Name the library (for example, "RazorClassLib"), > **Create** > **Next**. To avoid a file name collision with the generated view library, ensure the library name doesn't end in `.Views`.
* Select the **Target Framework**. Check **☑ Support pages and views** to support views. By default, only Razor components are supported. Select **Create**.
Expand Down Expand Up @@ -564,7 +564,7 @@ Razor views, pages, controllers, page models, [Razor components](xref:blazor/com

# [Visual Studio](#tab/visual-studio)

* From Visual Studio select **Create new a new project**.
* From Visual Studio's **Start Window**, select **Create a new project**. Alternatively, select the **File** > **New** > **Project/Solution**.
* Select **Razor Class Library** > **Next**.
* Name the library (for example, "RazorClassLib"), > **Create**. To avoid a file name collision with the generated view library, ensure the library name doesn't end in `.Views`.
* Select **Support pages and views** if you need to support views. By default, only Razor Pages are supported. Select **Create**.
Expand Down
Loading