Understanding Server-Side Blazor

Introduction

Blazor is a .NET Core web framework that runs C# code on the browser using WebAssembly. It offers an alternative to JavaScript frameworks like React, Angular, and Vue. A Blazor App offers several benefits over these alternatives, such as faster execution times and better performance. Blazor relies on Razor view syntax, which is a markup language similar to HTML. Blazor uses C# code to run in web browsers, and Blazor App code can be authored with Visual Studio. We can also create a standalone Blazer web assembly app without any server-side app.

You can also host Razor components in native mobile and desktop apps that render to a Web View control. Regardless of the hosting model, if you use Razor Components they'll work the same way. You can use the same Razor components in any of these models unchanged.

Blazor server hosting model

ASP.NET Core apps can be configured to use Blazor Server as the hosting model, which means that the app is executed on the server side instead of in a browser. Updating UI content and handling events happen over a SignalR connection using the WebSockets protocol. Blazor allows the scaling apps to handle multiple client connections.

The state on the server associated with each connected client is called a circuit. Circuits don't get tied to a specific network connection and can tolerate - temporarily - interrupted connections. In addition, clients can reconnect to the server when they want to even after going offline.

With a server-side Blazor app, each browser screen requires its circuit and components will be rehydrated by the server. If graceful termination occurs, the circuit along with any associated hardware or drivers is immediately released.

The Blazor script (blazor.server.js) establishes the SignalR connection with the server on the client's side. The script is served to the client-side app from an embedded resource in ASP.NET Core's shared framework. The client-side app is responsible for persisting and restoring its state as needed. From the docs: A hosted client app can interact with its backend server app over the network using a variety of messaging frameworks and protocols, such as web API, gRPC-web, and SignalR.

ASP.NEt CORE DOM-

Iron pdf.NET pdf library

IronPDF.NET is a .NET library for generating PDF documents and manipulating existing ones. It has a set of APIs to generate PDF documents in different ways - from rendering an existing HTML page to converting an image format to PDF. I have found to read, create & export PDFs from within Blazor Server Hosting Model Apps.

IronPDF supports the latest .NET Core version. It also supports the Blazor project type. In this article, we'll see how we can create PDFs in Blazor server apps using IronPDF. Explore more examples of Blazor server tutorials here.

Generate pdf in Blazor server apps

Let's see how Blazor server Apps work. I'll use the IronPDF library for generating PDFs in the Blazor server hosting model application. Let's see how to do it.

Step 1. Creating Blazor server app

Open Visual Studio and search for Blazor Server App in Application templates. Select it and hit the next button.

Template of new project-

Now give the proper name to the project and click the "next" button.

Configure your new project Iron PDF Blazor-

Select the latest .NET Core framework. You can choose any version according to your requirements but the latest version is recommended. After selecting the .NET framework, hit the Create button. It'll create a Blazor Server Application.

Additional Information-

Step 2. Install iron pdf

Now, it's time to install Iron PDF. Go to the tools from the top menu. From the dropdown, hover on "NuGet Package Manager" and from the sub-menu, select "Package Manager Console". It'll open the console for installing NuGet packages into your .NET Core project.

Nuget Package Manager-.

Run the following command in the Package Manager Console.

install-package IronPDF

Alternatively, use the Nuget Package Manager GUI and search for IronPDF.

This will start installing IronPDF in our project.

Package Manager Console Host Version -

Step 3. Create Razor component

Now create a new Razor component in the "Pages" folder.

Right-click on the "Pages" folder and from the submenu of the "Add" option, select "New Item". It'll open a new dialog box.

New Item-

Select Razor Component put "GeneratePDF" as the name and hit the "Add" button. The razor component will be added to the "Pages" folder.

Add New item -Iron PDF Blazor-

Now open "GeneratePDF.razor" and write the following server-side code.

At first, I define the page route and provide the name "/pdf". After that, I inject IJSRuntime JS to save the generated PDF file. I create the Page Title and heading using HTML tags. After that, I create Textarea and bind it with the variable "htmlString". I'll use the "htmlString" variable to get the text written in the text area for generating PDF. I'll define the htmlString variable in the code part later. I create a button and bind it with the CreatePDF function using the onclick function. Let's move to the code part.

In the code, I create the variable name "htmlString". After that, I create an async function CreatePDF. In the function, I initiate "ChromePdfRenderer" and use the "RenderHtmlAsPdf" function to convert HTML to PDF. After that, I convert the generated PDF into a stream object to make it a downloadable file and invoke the JS function.

@page "/pdf"
@inject IJSRuntime JS
<PageTitle>Create PDF</PageTitle>
<h1>Create PDF</h1>
<div class="form-outline">
    <textarea class="form-control w-50" id="htmltopdf" rows="8" cols="16" @bind="htmlString"></textarea>
    <button class="btn btn-primary mt-4" @onclick="CreatePDF">Create PDF</button>
</div>
@code {
    private string htmlString { get; set; } = default!;
    private async Task CreatePDF()
    {
        var render = new IronPdf.ChromePdfRenderer();
        var doc = render.RenderHtmlAsPdf(htmlString);
        using var Content = new DotNetStreamReference(stream: doc.Stream);
        await JS.InvokeVoidAsync("SubmitHTML", "ironpdf.pdf", Content);
    }
}

Step 4. JS code for file downloading

Write the following JS code at the bottom of the "_Layout. cshtml" file. This JS code will help to download the PDF file.

<script>
    window.SubmitHTML = async (fileName, contentStreamReference) => {
        const arrayBuffer = await contentStreamReference.arrayBuffer();
        const blob = new Blob([arrayBuffer]);
        const url = URL.createObjectURL(blob);
        const anchorElement = document.createElement('a');
        anchorElement.href = url;
        anchorElement.download = fileName ?? '';
        anchorElement.click();
        anchorElement.remove();
        URL.revokeObjectURL(url);
    }
</script>

Step 5. Add pdf to generate a page in the navbar

Now add the following code in "NavMenu.razor" to add a nav menu to access our GeneratePDF page.

<div class="nav-item px-3">
    <NavLink class="nav-link" href="pdf">
        <span class="oi oi-list-rich" aria-hidden="true"></span> PDF
    </NavLink>
</div>

Step 6. Run the Blazor server app

Now run the Blazor App project. You'll see the output as shown below:

Create PDF-

We can write any text in the text and hit the Create PDF button to generate a PDF.

Step 7. Put HTML code in textarea

Write the following HTML code in the text area for converting it into PDF. It is the HTML of an invoice.

<!DOCTYPE html>
<html lang="en">

<head>
    <meta charset="utf-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1" />
    <title>A simple, clean, and responsive HTML invoice template</title>
    <!-- Favicon -->
    <link rel="icon" href="./images/favicon.png" type="image/x-icon" />
    <!-- Invoice styling -->
    <style>
        body {
            font-family: "Helvetica Neue", "Helvetica", Helvetica, Arial, sans-serif;
            text-align: center;
            color: #777;
        }

        body h1 {
            font-weight: 300;
            margin-bottom: 0px;
            padding-bottom: 0px;
            color: #000;
        }

        body h3 {
            font-weight: 300;
            margin-top: 10px;
            margin-bottom: 20px;
            font-style: italic;
            color: #555;
        }

        body a {
            color: #06f;
        }

        .invoice-box {
            max-width: 800px;
            margin: auto;
            padding: 30px;
            border: 1px solid #eee;
            box-shadow: 0 0 10px rgba(0, 0, 0, 0.15);
            font-size: 16px;
            line-height: 24px;
            font-family: "Helvetica Neue", "Helvetica", Helvetica, Arial, sans-serif;
            color: #555;
        }

        .invoice-box table {
            width: 100%;
            line-height: inherit;
            text-align: left;
            border-collapse: collapse;
        }

        .invoice-box table td {
            padding: 5px;
            vertical-align: top;
        }

        .invoice-box table tr td:nth-child(2) {
            text-align: right;
        }

        .invoice-box table tr.top table td {
            padding-bottom: 20px;
        }

        .invoice-box table tr.top table td.title {
            font-size: 45px;
            line-height: 45px;
            color: #333;
        }

        .invoice-box table tr.information table td {
            padding-bottom: 40px;
        }

        .invoice-box table tr.heading td {
            background: #eee;
            border-bottom: 1px solid #ddd;
            font-weight: bold;
        }

        .invoice-box table tr.details td {
            padding-bottom: 20px;
        }

        .invoice-box table tr.item td {
            border-bottom: 1px solid #eee;
        }

        .invoice-box table tr.item.last td {
            border-bottom: none;
        }

        .invoice-box table tr.total td:nth-child(2) {
            border-top: 2px solid #eee;
            font-weight: bold;
        }

        @media only screen and (max-width: 600px) {
            .invoice-box table tr.top table td {
                width: 100%;
                display: block;
                text-align: center;
            }

            .invoice-box table tr.information table td {
                width: 100%;
                display: block;
                text-align: center;
            }
        }
    </style>
</head>

<body>
    <div class="invoice-box">
        <table>
            <tr class="top">
                <td colspan="2">
                    <table>
                        <tr>
                            <td class="title">
                                <img src="https://cdn.logojoy.com/wp-content/uploads/2018/05/01104800/1050-768x591.png"
                                    alt="Company logo" style="width: 100%; max-width: 300px" />
                            </td>
                            <td>
                                Invoice #: 123<br />
                                Created: January 1, 2015<br />
                                Due: February 1, 2015
                            </td>
                        </tr>
                    </table>
                </td>
            </tr>
            <tr class="information">
                <td colspan="2">
                    <table>
                        <tr>
                            <td>
                                Sparksuite, Inc.<br />
                                12345 Sunny Road<br />
                                Sunnyville, TX 12345
                            </td>
                            <td>
                                Acme Corp.<br />
                                John Doe<br />
                                [email protected]
                            </td>
                        </tr>
                    </table>
                </td>
            </tr>
            <tr class="heading">
                <td>Payment Method</td>
                <td>Check #</td>
            </tr>
            <tr class="details">
                <td>Check</td>
                <td>1000</td>
            </tr>
            <tr class="heading">
                <td>Item</td>
                <td>Price</td>
            </tr>
            <tr class="item">
                <td>Website design</td>
                <td>$300.00</td>
            </tr>
            <tr class="item">
                <td>Hosting (3 months)</td>
                <td>$75.00</td>
            </tr>
            <tr class="item last">
                <td>Domain name (1 year)</td>
                <td>$10.00</td>
            </tr>
            <tr class="total">
                <td></td>
                <td>Total: $385.00</td>
            </tr>
        </table>
    </div>
</body>

</html>

After writing the code, hit the "Create PDF" button.

Create Html PDF-.

You will see that the PDF file with the name "ironpdf.pdf" will be downloaded to your computer via the browser - directly from the Blazor App.

Pdf

Step 8. Open the pdf file

Now, open the PDF file. You'll see the following output. IronPDF generates excellent PDFs and preserves every detail and styling.

Glycon-

Source code: You can get the source code from GitHub.

Conclusion

Blazor Server has many advantages. The download size is very small and the app loads very fast. It can take advantage of server capabilities e.g. use of .NET core APIs. For some browsers that don't support WebAssembly, Blazor Server works with these browsers very well.

But Blazor Apps have some limitations like it requires ASP.NET Core Server. So, Serverless deployment scenarios are not applicable. Here is the chart so you can understand the benefits and disadvantages of each model easily.

Feature-

IronPDF is a very useful library that supports every type of project in .NET (including Framework, Core, and .NET 5-7). It doesn't require any external library to support it, making it ideal for the development of your next Blazor App.

Thank you for reading the article. If you like it, please share it with your friends.

8 Comments

Join the conversation! Your thoughts help the community grow.

Riaan G8y ago
Has anyone used [Authorize] with Server-side Blazor? I guess the "@page" is now the PageModel. Using your example, it would be great to protect the /fetchdata resource seeing that Server-side has full access to .net core.
Ano Mepani8y ago
Https://youtu.be/7Eh_l7jEcCo nice to see this article used in reference purpose in asp.net community standup meeting 5:00 minute
- Ankit Sharma8y ago
  WOW.. This is great. I was unaware of this. Thanks for the info.
- Ano Mepani8y ago
  Your Welcome, I think you can mention this youtube link in your article so, people can view as part of an article and its also motivation for others as well.
Nen Ne8y ago
I could just use webapi instead of Blazor server, which gives me everything. am i missing something here ??
- Ankit Sharma8y ago
  You will get some benefits with server-side Blazor over traditional Blazor. Please look at the "advantage of server-side Blazor " section to get a better understanding. Also this feature is introduced with Blazor 0.5.0 release and expected to improve with future releases.
- Mahesh Chand8y ago
  In future, everything in Blazor is also not a bad point, rather than managing a separate Web API project.
Georgi Vatsov8y ago
Very useful article. Thank you. Just a minor addition: another difference in the Blazor server-side app in comparison to the client-side is that in the startup file we have "app.UseServerSideBlazor<App.Startup>();" instead of "app.UseBlazor<Client.Program>();"