Blazor: .NET in Your Browser

My last speaking engagement of 2019 was during a webinar for the wonderful technology community in Nepal. I provided an introduction to Blazor and walked through some of its more powerful features including components, service registration, JavaScript interoperability and using existing .NET Standard Libraries. If you're new to Blazor, this is a one hour investment I'm confident you will benefit from.

The full presentation, including Q&A, is available at: Blazor: .NET in Your Browser:

For a hands-on lab with a full walk through of various features, check out this repository:

JeremyLikness / blazor-wasm

Blazor and WebAssembly examples (part of a Blazor presentation)

Blazor and WebAssembly

Get your Free Azure Account

This repository contains samples for a presentation about using C# and .NET in the browser using WebAssembly with Blazor.

▶ Get Started with Blazor

👋🏻 Introduction/Overview of Blazor

🔪 Intro to Razor Components

This repository is continuously built and deployed using free Azure Pipelines. If you're interested in how it was setup and configured to build automatically and deploy to low cost Azure Storage Static Websites, read Deploy WebAssembly from GitHub to Azure Storage Static Websites with Azure Pipelines.

Presentation

🎦 You can download the related PowerPoint presentation here.

To see how Blazor compares to other SPA frameworks like Angular, read: Angular vs. Blazor.

Demos

This section contains step-by-step instructions to execute each of the demos.

Pre-requisites

The following should be installed for the demos to work:

• emscripten for the asm.js and WebAssembly demos
• http-service (node.js) to serve the…

View on GitHub

As always, questions and feedback are welcome.

Regards,

Comments

[Shaiju T]

Thanks, I have one more question.

First it was Asp.NET Web Form then
ASP.NET MVC then
Asp.NET Core and now its Blazor.NET

So should I learn first Asp.NET Core or Blazor.NET ? Which is going to dominate the future ?

[Jeremy Likness ⚡️]

Blazor doesn't replace ASP.NET. One is a client-side technology, the other is a server-side technology. If you want to stand up Web APIs, learning ASP.NET makes sense as the way to marshal data to your Blazor app. Much of the technology is complementary: the way you register services, etc. is consistent across the stacks.

[Shaiju T]

Thanks for the reply. Appreciate. 😃 👍

[Shaiju T]

We can develop client side apps using plain JavaScript or Angular, React etc and We can make Server Side Apps using .NET , Java, PHP etc then What is the major use of Blazor ? Why should I learn it ?

[Jeremy Likness ⚡️]

There are several reasons why companies are adopting Blazor. The most popular reason is code reuse. Existing .NET libraries that contain business logic can be used "as is" by a Blazor client. This allows for consistency between the client and server without resorting to projection or duplicating code. Other reasons include:

• Existing skills: C#, .NET and even Razor templates are skills used by existing .NET, ASP.NET, and MVC developers that are easily transferable
• Platform reach: many shops have existing WPF/UWP apps that impose a platform requirement and the overhead of managing installations, whereas Blazor will run in any modern browser
• Migration: when migrating from existing solutions, there is far more code reuse possible with Blazor than there is moving to an Angular/React/Vue solution
• Ecosystem: as I demonstrated for markdown, there are many existing .NET projects that solve common problems and can be integrated "as is" with Blazor
• Tooling: Blazor works well with existing .NET developer tools like Visual Studio 2019 and Visual Studio Code

For a shop already invest in Angular/React etc. I don't see any compelling reason to switch. For a shop looking to migrate code or build new projects and use existing .NET skills, Blazor is a very viable solution.

[John Munro]

I don't want .net on the browser, easy and simpler to just use JavaScript/TypeScript

[Oscar]

That's an opinion, not an argument. The author did a good job, and Blazor is a good way to use WebAssembly to avoid JS and its problems.