Blazor component and Blazor rendering modes

Our TWPdfViewer is a Razor class library component.

It has 3 possible render modes in Blazor server app or in your ASP.NET Core RazorPages/MVC web applications

1. ServerPrerendered

Renders the component into static HTML and includes a marker for a Blazor Server app. When the user-agent starts, this marker is used to bootstrap a Blazor app.

2. Server

Renders a marker for a Blazor Server app. Output from the component isn't included. When the user-agent starts, this marker is used to bootstrap a Blazor app.

3. Static

Renders the component into static HTML.

For WebAssembly app, from .NET 5, for hosted WebAssembly, available render modes are:

1. WebAssembly

Renders a marker for a Blazor WebAssembly app for use to include an interactive component when loaded in the browser. The component isn't prerendered. This option makes it easier to render different Blazor WebAssembly components on different pages.

2. WebAssemblyPrerendered

Prerenders the component into static HTML and includes a marker for a Blazor WebAssembly app for later use to make the component interactive when loaded in the browser.

Static rendering

TWPdfViewer doesn't have any need for interactivity with the server so recommended way is to use Static rendering mode (for Blazor Server app) or WebAssembly render mode (for WebAssembly web apps), but it will work also for other render modes.

In case static render is used, it is a mandatory to set additional parameter IsStatic="Yes".

More about integrating components from official documentation: Component tag helper