Hey Reader,

In this week's newsletter, I'm focusing on a fundamental yet often misunderstood aspect of Blazor in .NET 8 - prerendering in the new render modes (Server, WebAssembly, and Auto).

🚀 Prerendering Issue Resolution Video

You have two choices: watch the video below, which illustrates the common issue with prerendering, or continue reading for the code details.

​

🌟 Disabling Prerendering in Blazor with .NET 8

It's quite straightforward. When you opt for one of Blazor's new rendering modes in .NET 8 - Server, WebAssembly, or Auto - you'll need to use the @rendermode directive. This directive allows you to select one of these modes for either a page or a component:

Here's an important note: if you're loading data, for example, prerendering is on by default. This can cause an unsightly flicker. Observe in the gif below how the values change twice upon page reload.

That's prerendering for you. While it might be beneficial for SEO, there are times when it's not desirable due to the negative impact on user experience.

To address this, simply instantiate the render mode of your choice and set the prerender parameter to false.

This solution is applicable to all render modes and is also useful if you're looking to modify the effect for specific components rather than an entire page.

💌 Now It's Your Turn! How do you feel about prerendering? When and where would you use it?

A huge thank you to our community, and special gratitude to my Patrons for their steadfast support. Your contributions are vital to the success of this newsletter and my YouTube channel.

Excited for our next coding journey together. Stay safe and happy coding! 💻

Take care,

Patrick