Episode 452: Scott Hanselman on .NET

WebAssembly

The integration of .NET Core runtime with WebAssembly is a significant advancement for the Blazor framework. Scott Hanselman explains that the .NET Core runtime, once considered bulky, is now compact enough to fit within WebAssembly, making it comparable in size to common web assets like images 1. This integration allows developers to run .NET applications in the browser without relying heavily on JavaScript. Hanselman highlights the flexibility of Blazor, which can operate both client-side and server-side, providing developers with the choice of where to execute their code 1.

Blazor is seeing huge pickup, particularly in people who have found JavaScript to be somewhat daunting.

--- Scott Hanselman

This approach is gaining traction among developers who prefer C# over JavaScript, as it simplifies the development of web applications 2.

   

Blazor Models

Blazor offers two primary development models: Blazor WebAssembly and Blazor Server. Scott Hanselman describes how Blazor WebAssembly allows .NET applications to run directly in the browser, leveraging the power of WebAssembly to execute C# code client-side 1. Alternatively, Blazor Server enables the execution of .NET code on the server, with client-side interactions managed through WebSockets, providing a seamless experience without the need for JavaScript 1.

You can actually not run the .NET framework and the .NET Core, rather, pardon me, on the client side, but you can have it run on the server side.

--- Scott Hanselman

This flexibility is part of what makes Blazor appealing, as it caters to a wide range of development needs and preferences 3.