Blazor: Client Side vs. Server Side: Hands on Development and Deployment

We will look at the main differences between Client Side Blazor, and Server Side Blazor. We will discuss situations and scenarios in which one should be favored over the other. We will develop a small app & deploy it twice on Azure: As a Client Side Blazor App, and as a Server Side Blazor App.

[@Courserasrikanthdrk]

thanks and amazed by the logic

[@Teewatt]

How big is the runtime that needs to be downloaded the first time with client-side Blazor?

[@swankyshivy]

how safe is this web assembly code as its client side. is it that user can see all source code. how do you hide sensitive info like exact table names and columns,connection strings, credentials etc?

[@johnnyxp64]

is like or harder to reverse as the normal assembly. That's why and the name.
anything will be compiled to this machine language and run at native speeds.

[@swankyshivy]

@@johnnyxp64 u saying the code will be easy or hard to view? if its easy to view then it will make it more vulnerable to attacks as the person will know exactly wht code doing

[@heliumfilledstamp]

@@swankyshivy just like any client, never put authoritative logic in blazor webassembly. Its akin to angular or react, you wouldnt put core logic in there, would you? Instead, you have it call a server webapi to do the logic.

[@alexzzz3588]

JavaScript shell be considered as an assistant layer that can manipulate with DOM on the client side in order to improve user experience. If a user disables JavaSript a web-site still works, however without some effects and/or browser uploads all data from a server. What about Blazor? Is it designed to work as JavaScript? How can I use server-side technologies like MVC and Razor Pages with Blazor in one project? With JavaScript I can do it easy. Is there Microsoft documentation regarding above?

[@JeremyCaney]

In most browsers, disabling JavaScript also disables Web Assembly. Some browsers allow Web Assembly to be specifically disabled independent of JavaScript. As far as MVC: Yes, you can embed a Blazor Component inside of a Razor Page or view. In fact, that exact scenario is discussed in the previous talk, “Modern Web Development with Blazor & .NET 5” with Dan Roth and Javier Calvarro.

[@adds-kz3oc]

You need JS to load the .NET Wasm runtime so disabling it will also disable the app.

[@alexzzz3588]

@@JeremyCaney Thank you for advise! I've missed the previous video with Daniel Roth. It casts light on handful of things. In fact too many I've gotten lost in them ). I hope proper documentation explains everything.

[@Rogueixpresents]

realllllly not a fan about the .net runtime being downloaded on the client when i am just making a simple static page

[@dule88rs]

Good presentation, but such a strange demo application :D

[@matthewspencer6669]

Haha, I agree. But keeps it fun. Although it would have been nice to see a proper UI interaction difference between server/client. Client-side the boxes should move every tick and follow exactly, server should show lag.

[@dule88rs]

@@matthewspencer6669 yes, I was expecting the same thing.

[@ShaneCourtrille]

This is the standard Angular tutorial app

[@matthewspencer6669]

@@ShaneCourtrille Well that makes more sense. But still... a low-latency client-side demo would have suited better. It certainly didn't make me want to jump in and make an interactive web app using Blazor

[@fieryscorpion]

Blazorserver IMHO doesn’t bring much value to innovation and it’s just a noise to the choices.
.NET Core with Razor Pages is far better development experience than Blazorserver.
On the other hand Blazor WASM is Amazing!
.NET Core Web Api in the backend and Blazor WASM in the frontend can make amazing apps!

[@sunflower7360]

The author is singing in stead of talking.