Keene Systems builds business web applications with Blazor, Microsoft’s framework for creating interactive screens in C# instead of JavaScript. Blazor is part of ASP.NET Core, so it sits naturally beside the ASP.NET and SQL Server systems we have built since 2002. We use it where screens need to behave like desktop software.
What Blazor is, in plain English
Traditionally a web application is written in two languages: one on the server, such as C#, and JavaScript in the browser. Two languages mean two sets of skills, two sets of bugs and business rules written twice.
Blazor removes the split. The screens are written in C#, the same language as the rest of an ASP.NET application. A rule such as “an order over a credit limit needs approval” is written once and used everywhere. For a company that already runs on Microsoft technology, that means a smaller codebase and one team that can work on all of it.
When Blazor is worth considering
You are building a new internal business application on the Microsoft stack.
You have a Web Forms application to replace and want the least disruptive route.
Your developers know C# well and JavaScript less well.
You want desktop-style screens that run in a browser.
You are tired of business rules being written once on the server and again in the browser.
Blazor Server, WebAssembly and the choice between them
Blazor can run in more than one way, and one application can mix them:
Blazor Server runs the logic on your server and updates the browser over a live connection. It loads quickly and keeps the code off the user’s machine. It suits internal business systems where everyone has a steady connection.
Blazor WebAssembly runs the application inside the user’s browser. It can keep working through a poor connection and puts less load on the server. It suits public-facing tools and field use.
Mixed rendering lets each page or component use whichever mode fits it, with plain server-rendered pages where nothing interactive is needed.
Choosing well at the start saves rework later. It is one of the first things we settle in the design.
Where Blazor fits best
Data-heavy internal systems. Grids, filters, forms and dashboards that staff use all day.
Replacing Web Forms. Blazor’s component model feels familiar to anyone who knows Web Forms, which makes it a natural destination when an old Web Forms application is modernized.
Replacing desktop applications. Screens that used to be WinForms or VB6 can be rebuilt in the browser without losing their responsiveness.
Companies with C# developers. Your own staff can read and extend the whole application.
We also use Blazor ourselves: it is what we build our own internal business tools on.
Blazor vs React and Angular
React and Angular are JavaScript frameworks, and both are excellent. We build with them too. In short:
Blazor fits a business application on the Microsoft stack, built by a team that is strongest in C#, where one language from database to screen is worth having.
React fits a public-facing site, a product that also needs a phone app, or a team of JavaScript developers. The full comparison is in Blazor vs React.
Angular is a complete, strongly structured framework written in TypeScript. It appeals to the same large-application teams that Blazor does, and the deciding question is usually whether those teams work in C# or in TypeScript.
Whichever is chosen, the server side can be the same ASP.NET Core application, so the choice of screen technology does not lock in everything else.
How a Blazor project works
Start with the users. Who will use the screens, on what devices and over what kind of connection.
Pick the hosting model. Server, WebAssembly or a mix, decided by those answers and not by habit.
Agree the screens. Layouts are sketched and reviewed with the people who will sit in front of them.
Build component by component. Reusable pieces such as grids and forms are built once and used throughout.
Try it under real conditions. Real data, real users and the slowest connection anyone will have.
Keep improving it. The developers who built it stay on call for changes, without minimums or monthly commitments.
Blazor is used to build interactive web applications in C# instead of JavaScript. It is most often used for business systems with data-heavy screens, such as dashboards, order entry, scheduling and administration tools.
Is Blazor ready for production business applications?
Yes. Blazor is a supported part of ASP.NET Core, is developed by Microsoft and has been used in production business systems for years.
How does Blazor compare with React?
Blazor screens are written in C# and React screens in JavaScript. Blazor tends to suit internal business systems maintained by C# developers, and React tends to suit public sites and JavaScript teams. Our Blazor vs React page sets out the comparison in full.
Can Blazor replace an ASP.NET Web Forms application?
Yes. Blazor’s component model is close to the way Web Forms applications are organized, which makes it a common destination when Web Forms systems are modernized.
Can Blazor be added to an existing ASP.NET Core application?
Yes. Blazor components can be added to an existing ASP.NET Core MVC or Razor Pages application one screen at a time.
Keene Systems has built custom business software since 1987. We are veteran-owned, and our 50+ professionals have delivered systems for companies including Hormel, McCormick, IBM and Dartmouth-Hitchcock. See our client list.
Talk to a Blazor development team