Consume ASP.NET Core Razor components from Razor class libraries

Components can be shared in a Razor class library (RCL) across projects. Include components and static assets in an app from:

  • Another project in the solution.
  • A referenced .NET library.
  • A NuGet package.

Just as components are regular .NET types, components provided by an RCL are normal .NET assemblies.

Create an RCL

  1. Create a new project.
  2. In the Create a new project dialog, select Razor Class Library from the list of ASP.NET Core project templates. Select Next.
  3. In the Configure your new project dialog, provide a project name in the Project name field or accept the default project name. Examples in this topic use the project name ComponentLibrary. Select Create.
  4. In the Create a new Razor class library dialog, select Create.
  5. Add the RCL to a solution:
    1. Open the solution.
    2. Right-click the solution in Solution Explorer. Select Add > Existing Project.
    3. Navigate to the RCL's project file.
    4. Select the RCL's project file (.csproj).
  6. Add a reference to the RCL from the app:
    1. Right-click the app project. Select Add > Project Reference.
    2. Select the RCL project. Select OK.

If the Support pages and views checkbox is selected to support pages and views when generating the RCL from the template:

  • Add an _Imports.razor file to root of the generated RCL project with the following contents to enable Razor component authoring:

    @using Microsoft.AspNetCore.Components.Web
  • Add the following SupportedPlatform item to the project file (.csproj):

      <SupportedPlatform Include="browser" />

    For more information on the SupportedPlatform item, see the Browser compatibility analyzer for Blazor WebAssembly section.

Consume a Razor component from an RCL

To consume components from an RCL in another project, use either of the following approaches:

  • Use the full component type name, which includes the RCL's namespace.
  • Individual components can be added by name without the RCL's namespace if Razor's @using directive declares the RCL's namespace. Use the following approaches:
    • Add the @using directive to individual components.
    • include the @using directive in the top-level _Imports.razor file to make the library's components available to an entire project. Add the directive to an _Imports.razor file at any level to apply the namespace to a single component or set of components within a folder. When an _Imports.razor file is used, individual components don't require an @using directive for the RCL's namespace.

In the following examples, ComponentLibrary is an RCL containing the Component1 component. The Component1 component is an example component automatically added to an RCL created from the RCL project template that isn't created to support pages and views.


If the RCL is created to support pages and views, manually add the Component1 component and its static assets to the RCL if you plan to follow the examples in this article. The component and static assets are shown in this section.

Component1.razor in the ComponentLibrary RCL:

<div class="my-component">
    This component is defined in the <strong>ComponentLibrary</strong> package.

In the app that consumes the RCL, reference the Component1 component using its namespace, as the following example shows.


@page "/consume-component-1"

<h1>Consume component (full namespace example)</h1>

<ComponentLibrary.Component1 />

Alternatively, add a @using directive and use the component without its namespace. The following @using directive can also appear in any _Imports.razor file in or above the current folder.


@page "/consume-component-2"
@using ComponentLibrary

<h1>Consume component (<code>@@using</code> example)</h1>

<Component1 />

For library components that use CSS isolation, the component styles are automatically made available to the consuming app. There's no need to link the library's individual component stylesheets in the app that consumes the library. For the preceding examples, Component1's stylesheet (Component1.razor.css) is included automatically.

Component1.razor.css in the ComponentLibrary RCL:

.my-component {
    border: 2px dashed red;
    padding: 1em;
    margin: 1em 0;
    background-image: url('background.png');

The background image is also included from the RCL project template and resides in the wwwroot folder of the RCL.

wwwroot/background.png in the ComponentLibrary RCL:

Diagonally-striped background image from the RCL project template

Create an RCL with static assets

An RCL's static assets are available to any app that consumes the library.

Place static assets in the wwwroot folder of the RCL and reference the static assets with the following path in the app: _content/{LIBRARY NAME}/{PATH AND FILE NAME}. The {LIBRARY NAME} placeholder is the library name. The {PATH AND FILE NAME} placeholder is path and file name under wwwroot.

The following example demonstrates the use of RCL static assets with an RCL named ComponentLibrary and a Blazor app that consumes the RCL. The app has a project reference for the ComponentLibrary RCL.

The following Jeep® image is used in this section's example. If you implement the example shown in this section, right-click the image to save it locally.

wwwroot/jeep-yj.png in the ComponentLibrary RCL:

Jeep YJ®

Add the following JeepYJ component to the RCL.

JeepYJ.razor in the ComponentLibrary RCL:


    <img alt="Jeep YJ&reg;" src="_content/ComponentLibrary/jeep-yj.png" />

Add the following Jeep component to the app that consumes the ComponentLibrary RCL. The Jeep component uses:

  • The Jeep YJ® image from the ComponentLibrary RCL's wwwroot folder.
  • The JeepYJ component from the RCL.


@page "/jeep"
@using ComponentLibrary

<div style="float:left;margin-right:10px">
    <h3>Direct use</h3>

        <img alt="Jeep YJ&reg;" src="_content/ComponentLibrary/jeep-yj.png" />

<JeepYJ />

    <em>Jeep</em> and <em>Jeep YJ</em> are registered trademarks of 
    <a href="">FCA US LLC (Stellantis NV)</a>.

Rendered Jeep component:

Jeep component

For more information, see Reusable Razor UI in class libraries with ASP.NET Core.

Supply components and static assets to multiple hosted Blazor apps

For more information, see Host and deploy ASP.NET Core Blazor WebAssembly.

Browser compatibility analyzer for Blazor WebAssembly

Blazor WebAssembly apps target the full .NET API surface area, but not all .NET APIs are supported on WebAssembly due to browser sandbox constraints. Unsupported APIs throw PlatformNotSupportedException when running on WebAssembly. A platform compatibility analyzer warns the developer when the app uses APIs that aren't supported by the app's target platforms. For Blazor WebAssembly apps, this means checking that APIs are supported in browsers. Annotating .NET framework APIs for the compatibility analyzer is an on-going process, so not all .NET framework API is currently annotated.

Blazor WebAssembly and RCL projects automatically enable browser compatibility checks by adding browser as a supported platform with the SupportedPlatform MSBuild item. Library developers can manually add the SupportedPlatform item to a library's project file to enable the feature:

  <SupportedPlatform Include="browser" />

When authoring a library, indicate that a particular API isn't supported in browsers by specifying browser to UnsupportedOSPlatformAttribute:

private static string GetLoggingDirectory()

For more information, see Annotating APIs as unsupported on specific platforms (dotnet/designs GitHub repository.

JavaScript isolation in JavaScript modules

Blazor enables JavaScript isolation in standard JavaScript modules. JavaScript isolation provides the following benefits:

  • Imported JavaScript no longer pollutes the global namespace.
  • Consumers of the library and components aren't required to manually import the related JavaScript.

For more information, see Call JavaScript functions from .NET methods in ASP.NET Core Blazor.

Build, pack, and ship to NuGet

Because Razor class libraries that contain Razor components are standard .NET libraries, packing and shipping them to NuGet is no different from packing and shipping any library to NuGet. Packing is performed using the dotnet pack command in a command shell:

dotnet pack

Upload the package to NuGet using the dotnet nuget push command in a command shell.


Jeep and Jeep YJ are registered trademarks of FCA US LLC (Stellantis NV).

Additional resources