The Worst Thing about Blazor

[@trxe420]

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.

[@wiepcorbier]

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

[@Thyrius82]

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.

[@pkop4]

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.

[@liberateamerica]

It's so horrible. Having 20 tabs open for just a few changes is so annoying. I hate working with front end in VS..

[@matheosmattsson2811]

@@liberateamerica @pkop4 I think you guys are talking about two different things. I think the different profile thing is quite nice. It does not mess with your "real" history, cache, etc. All your localhost nonsense is kept separate from your daily browsing.. For me, using chrome, it opens chrome when debugging and if I kill that chrome instance, it will also kill the debugging session and the dev-server.. It won't spawn new tabs if I re-open, as the debugging session is closely tied to the lifetime of the browser instance. Killing either will kill the other. This is when running with debugging. If running without a debugger, it may well open in my regular browser and spawn a new tab etc. Keep in mind, we are using Blazor Web Assembly, not Blazor Server nor Blazor Web App. I don't know how those behave. But yes, I agree, hot reload in blazor is unreliable and crap, but it is way better nowadays than it used to be.

[@dirkschannel5817]

I started to migrate old Web Forms apps to Blazor when .NET 8 shipped. Previous to .NET I didn’t see the benefits to replace a legacy, but perfect working performant app from .NET Framework that might be supported for the next two decades… So far I like Blazor. It shines at CRUD apps. If it’s the right choice for customer facing app, I don’t know.

[@rmbl349]

Thats not a blazor problem, Thats a VS/WIndows problem. Holy crap I hate it when people get thing mixed up and say framework/technollagy is bad...

[@RamPageMMA]

@Snickerv12 configure the launch settings in the Properties folder

[@longcall911]

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? :-)

[@istovall2624]

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

[@jimiscott]

100% I understand the complexity around hot reload (especially WASM), but MS really should be focussing their efforts on this.

[@shabanelmogy7912]

Blazor Stable In Production ?

[@Mark-D-Inman]

Most definitely.

[@sokoo1978]

@@Mark-D-Inman How do you solve updates? I could not find a nice way, users have to CTRL-F5 to get the latest version of the app. Quite annoying.

[@jimiscott]

Yes