Blazor as a new front-end technology for Microsoft .NET
![](https://cdn.prod.website-files.com/65fbeffcc48e3bcdc6a414e8/664db8535f2aa93cd214efae_Brian.png)
In short:
- Blazor is increasingly being recommended as a front-end technology for .NET solutions because of its ability to use “regular” C# code, making it easy to integrate with existing libraries and accelerate development in compact teams.
- Using Blazor offers benefits such as the ability to use a single codebase for both front-end and backend, so development does not depend on specific team members and allows full-stack solutions to be developed quickly.
Blazor as a new front-end technology for Microsoft .NET
There is a lot of continuous development in front-end technologies. We test and validate many frameworks in order to provide the right technology advice to our clients. Blazor is a technology that we are increasingly recommending for software solutions in .NET.
Blazor (#C and .NET front end)
We enjoy working with modern and proven technologies. Blazor complies with both. It is a relatively new technology within the .NET framework that has quickly proven to be a reliable solution. For our development projects within the .NET stack, we are therefore increasingly choosing to make use of this front-end technology.
The benefits of Blazor
The big advantage over other front-end frameworks such as Angular is that 'normal' C# code can be used to use Blazor. One agreement with Angular, for example, is that Blazor is also component based. In practice, for our .NET teams, the big advantage is that a single codebase can be used, from which the Blazor front-end can also make use of existing libraries. Because the technology quickly feels familiar to backend developers, they are now able to develop complete full-stack solutions in compact teams. This provides the necessary acceleration of projects, as development does not depend on the expertise of specific team members.