DEV Community

Discussion on: Blazor: .NET in Your Browser

Collapse
 
jeremylikness profile image
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.