{"id":19563,"date":"2022-12-06T09:56:02","date_gmt":"2022-12-06T08:56:02","guid":{"rendered":"https:\/\/www.codemotion.com\/magazine\/?p=19563"},"modified":"2022-12-06T09:56:06","modified_gmt":"2022-12-06T08:56:06","slug":"developing-industrial-iot-applications-with-blazor","status":"publish","type":"post","link":"https:\/\/www.codemotion.com\/magazine\/iot\/developing-industrial-iot-applications-with-blazor\/","title":{"rendered":"Developing Industrial IoT Applications with Blazor"},"content":{"rendered":"\n

Why is Blazor becoming so popular?<\/h2>\n\n\n\n

Web applications have been developed for approximately 30 years, and during this period both hardware and software technologies have undergone drastic changes. However, the nature of web applications and websites has essentially remained the same<\/strong>: we have a front-end layer exposed to the user and to the world, and a back-end layer, which contains internal data and logic.<\/p>\n\n\n\n

This means that building such an application requires at the very least a two-layered technological stack \u2013 with 3+ layer stacks being common to take care of databases, services, containers, etc. In the past, the internal complexity of web applications made many developers specialise in a specific layer of the stack. Front-end and back-end development is still an important issue in web development<\/strong>, and the promise of full-stack developers seems to be difficult to accomplish if we (as users or managers) also want all-round proficiency.<\/p>\n\n\n\n

Unsurprisingly, independent technologies evolved for both front-end and back-end development, the archetypical example being the divide between Javascript <\/a>and Java, which only have in common their C-like syntax<\/strong>. Later on, frameworks appeared on the market, but they were mostly containers for other technologies.<\/p>\n\n\n\n

The first actual improvement came with Node.js, which allowed the use of a single language both for front and back-end development, as well as for storage (e.g. in the MEAN stack).<\/p>\n\n\n\n

A similar breakthrough occurred with Blazor, which provides tools to fully develop and deploy web applications through a .NET interface that can also be installed on Linux and Mac OS<\/strong>. The idea is to let the developer use C# for each application-related need and to use XML and JSON configuration files.<\/p>\n\n\n\n

\"Blazor
Blazor enables industry-grade IoT solutions.<\/figcaption><\/figure>\n\n\n\n

Thus, Blazor lets the C# programmer use their mother tongue both for back and front-end<\/strong> development, and to fully leverage .NET libraries and the .NET underlying environment to build client applications. Moreover, and since it\u2019s interoperable with Javascript, Blazor can be integrated with existing front-end libraries if needed, calling them from C#.<\/p>\n\n\n\n

Razor-specific configuration files are used to describe components, which are UI widgets that can be used inside the client and that can interact with back-end logic. Blazor allows writing applications on the server to build UI components, and facilitates interaction in real-time via SignalR, an open-source library whose API allows to invoke functions on the client via server code (with .NET Core running on the server side).<\/p>\n\n\n\n

All in all, and due to these features, Blazor is convenient when a web application shares one or more of the following features:<\/p>\n\n\n\n