Create reusable UI using the Razor Class Library project in ASP.NET Core.

By Rick Anderson

Razor views, pages, controllers, page models, View components, and data models can be built into a Razor Class Library (RCL). The RCL can be packaged and reused. Applications can include the RCL and override the views and pages it contains. When a view, partial view, or Razor Page is found in both the web app and the RCL, the Razor markup (.cshtml file) in the web app takes precedence.

This feature requires .NET Core 2.1 SDK or later

View or download sample code (how to download)

Create a class library containing Razor UI

  • From the Visual Studio File menu, select New > Project.
  • Select ASP.NET Core Web Application.
  • Name the library (for example, "RazorClassLib") > OK. To avoid a file name collision with the generated view library, ensure the library name doesn't end in .Views.
  • Verify ASP.NET Core 2.1 or later is selected.
  • Select Razor Class Library > OK.

Add Razor files to the RCL.

We recommend RCL content go in the Areas folder.

Referencing Razor Class Library content

The RCL can be referenced by:

Walkthrough: Create a Razor Class Library project and use from a Razor Pages project

You can download the complete project and test it rather than creating it. The sample download contains additional code and links that make the project easy to test. You can leave feedback in this GitHub issue with your comments on download samples versus step-by-step instructions.

Test the download app

If you haven't downloaded the completed app and would rather create the walkthrough project, skip to the next section.

Open the .sln file in Visual Studio. Run the app.

Follow the instructions in Test WebApp1

Create a Razor Class Library

In this section, a Razor Class Library (RCL) is created. Razor files are added to the RCL.

Create the RCL project:

  • From the Visual Studio File menu, select New > Project.
  • Select ASP.NET Core Web Application.
  • Name the app RazorUIClassLib.
  • Verify ASP.NET Core 2.1 or later is selected.
  • Select Razor Class Library > OK.

Create the Razor Pages web app:

  • From Solution Explorer, right-click the solution > Add > New Project.
  • Select ASP.NET Core Web Application.
  • Name the app WebApp1.
  • Verify ASP.NET Core 2.1 or later is selected.
  • Select Web Application > OK.

Add Razor files and folders to the project.

  • Add a Razor partial view file named RazorUIClassLib/Areas/MyFeature/Pages/Shared/_Message.cshtml.
  • Replace the markup in RazorUIClassLib/Areas/MyFeature/Pages/Shared/_Message.cshtml with the following code:
<h3> WebApp1 _Message.cshtml partial view.</h3>

<p>RazorUIClassLib\Areas\MyFeature\Pages\Shared\_Message.cshtml</p>
  • Copy the _ViewStart.cshtml file from the WebApp1 project to RazorUIClassLib/Areas/MyFeature/Pages/_ViewStart.cshtml.

    The viewstart file is required to use the layout of the Razor Pages project.

Use the Razor UI library from a Razor Pages project

  • From Solution Explorer, right-click on WebApp1 and select Set as StartUp Project.
  • From Solution Explorer, right-click on WebApp1 and select Build Dependencies > Project Dependencies.
  • Check RazorUIClassLib as a dependency of WebApp1.
  • From Solution Explorer, right-click on WebApp1 and select Add > Reference.
  • In the Reference Manager dialog, check RazorUIClassLib > OK.

Run the app.

Test WebApp1

Verify the Razor UI class library is being used.

  • Browse to /MyFeature/Page1.

Override views, partial views, and pages

When a view, partial view, or Razor Page is found in both the web app and the Razor Class Library, the Razor markup (.cshtml file) in the web app takes precedence. For example, add WebApp1/Areas/MyFeature/Pages/Page1.cshtml to WebApp1, and Page1 in the WebApp1 will take precedence over Page1in the Razor Class Library.

In the sample download, rename WebApp1/Areas/MyFeature2 to WebApp1/Areas/MyFeature to test precedence.

Copy the RazorUIClassLib/Areas/MyFeature/Pages/Shared/_Message.cshtml partial view to WebApp1/Areas/MyFeature/Pages/Shared/_Message.cshtml. Update the markup to indicate the new location. Build and run the app to verify the app's version of the partial is being used.