Search

Die beliebtesten SPA-Webframeworks verwenden heutzutage alle JavaScript. Seit der Veröffentlichung von Blazor WebAssembly im Mai 2020 gibt es jedoch auch die Möglichkeit, clientseitige Webanwendungen mit C# anstelle von JavaScript zu erstellen. Da Blazor ein neues Framework ist und es noch nicht viel Forschung darüber gibt, ist es schwer zu entscheiden, ob es eine gute Idee ist, es in einer Produktionsumgebung zu verwenden oder nicht. Diese Bachelorarbeit beschäftigt sich mit der Frage, wie Blazor WebAssembly funktioniert und welche Projekte damit realisiert werden können. Dazu wird ein Vergleich zu einem etablierten JavaScript SPA-Framework, nämlich React.js, anhand einer Reihe von Kriterien gezogen. Die Kriterien bestehen aus Vollständigkeit des Angebots, Geschichte, Community, Browser-Support, Bibliotheken, DOM-Manipulation, erforderliche Fähigkeiten, Lines of Code, Tooling, Performance und Wiederverwendbarkeit von Code. Um die Kriterien zu testen, wurden zwei Anwendungen entwickelt: eine Anwendung mit React.js und eine weitere mit Blazor WebAssembly. Zusätzlich zu den beiden Anwendungen wurde bestehende Literatur verwendet, um die Kriterien zu beantworten. Zudem wurde ein Prototyp geschrieben, der die Anforderungen an eine einfache CRM-Anwendung umsetzt, um ein Gefühl für das Blazor WebAssembly Framework zu bekommen. Die Ergebnisse des Prototyps und der Vergleich zwischen den beiden Frameworks haben gezeigt, dass Blazor eine ernstzunehmende Option für die Entwicklung von Webanwendungen ist (vor allem, wenn im Backend ohnehin schon .NET verwendet wird) und dass es angesichts seines Alters recht ausgereift ist.Es muss jedoch auch berücksichtigt werden, dass vergleichbare JavaScript-Frameworks alleine aufgrund ihres längeren Bestehens ausgereifter und umfassender sind. Aus dem gleichen Grund werden sie auch viel häufiger im Unternehmensumfeld eingesetzt und haben eine viel größere Community. The most popular SPA web frameworks nowadays use all JavaScript. However, since the release of Blazor WebAssembly in May 2020, there is also the possibility to create client-side web application using C# instead of JavaScript. Since Blazor is a new framework and there is not much research about it yet, it is hard to decide whether it is a good idea to use it in a production environment or not. This bachelor thesis deals with the question of how Blazor WebAssembly works and which projects can be implemented with it. To achieve that, a comparison to an established JavaScript SPA framework, namely React.js, is drawn based on a set of criteria. The criteria consist of Completeness of Offering, History, Community, Browser Support, Libraries, DOM Manipulation, Skill requirements, Lines of Code, Tooling, Performance, and Code reusability. Two applications were developed to test the criteria, an application using React.js and another using Blazor WebAssembly. In addition to the two applications, existing literature was consulted to answer the criteria. Further, a prototype application was written that implements requirements for a simple CRM application in order to get a sense of the Blazor WebAssembly framework. The results of the prototype and the comparison between the two frameworks have shown that Blazor is a feasible option for web application development (especially if .NET is already used in the backend anyway) and that it is quite mature considering its age. Furthermore, it must also be taken into account that comparable JavaScript SPA frameworks are more mature and comprehensive simply due to their longer existence. For the same reason, they are also used much more frequently in the enterprise environment and have a much larger community. submitted by: Christian Sitzwohl Bachelorarbeit FH JOANNEUM 2022

Blazor WebAssembly is a new framework that was released in May 2020 that makes it possible to build client-side web applications using C# instead of using JavaScript for its frontend. The most popular web frameworks today are JavaScript based frameworks. This study aims to find out if Blazor is a viable option to use for developing web applications and if it is a well-established framework compared to JavaScript frameworks. To evaluate Blazor, a comparison is performed between Blazor and React on six criteria. The criteria are lines of code, cyclomatic complexity, state management, debugging tools, community, and libraries. To answer the criteria two applications was developed, one in the React framework and one in the Blazor framework. Besides the two applications, literature was gathered to answer the criteria. The results from the comparison showed Blazor was a Viable option to use for the development of web applications and that it has become established as a framework when taken its age in to consideration.

For my thesis work I have done an evaluation of the newly released Microsoft developed web framework Blazor. My methodology is based upon a couple of previous articles about evaluating web frameworks. From these articles I have gathered a number of criteria used in my evaluation: documentation, lines of code,community size, framework usage, framework maturity, framework freshness, browser support and framework cost. Additionally, since Blazor is based on C# instead of JavaScript, I have included a 9th criterion, comparing JavaScript with C#. Many of the criteria need some kind of counterpart for Blazor to be compared with, for this purpose I have mainly used the established web framework Angular, and in some cases Ember.js. When evaluating, I have not expected Blazor to exceed Angular. Rather I have counted all cases where Blazor can at least be considered comparable to Angular (or Ember.js) as favourable.I found that overall Blazor did very well in the comparison as 6 out of the 8 criteria I took from the articles evaluated favourably for Blazor. The two criteria where I found Blazor lacking were framework usage and framework maturity. While there are large numbers of showcases and example sites I did not find any large production websites developed with Blazor, and for obvious reasons the framework that was officially released earlier this year has yet to reach a mature state. Furthermore I found the extra criteria, JavaScript vs C#, was favourable to Blazor.Thus, my conclusion is that Blazor is certainly worth picking up for new projects. I argue that even though the framework is not yet fully mature it has come far in its short lifespan, and that even though Blazor is not widely used yet it is unlikely to go away considering that it is developed and supported by a large company like Microsoft.