The Worst Thing about Blazor

Blazor’s Hot Reload (also known as Edit and Continue) feature has been a massive hinderance to developers. But this isn’t as simple as ‘it doesn’t work’. It’s a misunderstood feature, and therefore misused. In this video, we explore Hot Reload in Blazor in detail, to see what functions well and what doesn't, and how you should use it to get the best productivity boost.

📖 Chapters
00:00 - Start
01:21 - Setup
02:25 - Razor
03:03 - CSS
04:22 - C# Variables
05:06 - C# Logic
06:11 - Method Signatures
07:08 - Breakpoints
07:51 - Real World

[trxe]

It should be called hot mess reload. I love Blazor, but this is crucial to get right.

[AkiraTTS]

I have also given up on hot reload. It works in the template app with a few components, but it breaks horribly if you have a proper sized app or if you have components that inherit a base class and you make a change in the base class.

[cheesypufs]

Why can't Microsoft just have one of their genius developers dedicate 1 month to solve this issue? This just looks like MS can't get their shit together.

[Thyrius]

In some cases it works, in some cases it does not. In practice this means that sometimes you will not notice that something is wrong until you restart the application.

[pkop]

The worst thing is when debugging it opens Edge with a new profile instead of your current profile in the browser window you already have opened, doesn't save settings etc.

[criticalanimation]

Ignorance is bliz, until Hot reload don`t do what Hot reload do.

[wiepcorbier]

Hot reload takes a few seconds too.
But I don't care about Hot reload that much.

[longcall]

Agreed that hot reload sucks. So, I write a bunch of code, run the app, tweak it and then "Restart Application" from the toolbar. It's not perfect, but what is? :-)

[istovall]

I have 2 production wasm apps in blazor. and i gotta say, i love it. but yea hot reload sucks.