{"@attributes":{"version":"2.0"},"channel":{"title":"CSharp on GerkinDev Devblog","link":"https:\/\/gerkin.dev\/en\/tags\/csharp\/","description":"Recent content in CSharp on GerkinDev Devblog","generator":"Hugo -- gohugo.io","language":"en","copyright":"\u00a9{year}, All Rights Reserved","lastBuildDate":"Sat, 15 Jan 2022 10:00:00 +0100","item":{"title":"A quick glance at Blazor WebAssembly","link":"https:\/\/gerkin.dev\/en\/blog\/a-quick-glance-at-blazor-wasm\/","pubDate":"Sat, 15 Jan 2022 10:00:00 +0100","guid":"https:\/\/gerkin.dev\/en\/blog\/a-quick-glance-at-blazor-wasm\/","description":"<p>In 2018, <em>&#x1f47f; Microsoft<\/em> released its new framework, <em>Blazor<\/em>, which tease MVVM capabilities through component-oriented <em>AJAX<\/em> or <em>WebAssembly<\/em> application builds. 4 years later (and with many improvements &amp; versions), what is the current state of <em>Blazor<\/em>?<\/p>\n<p>In this article, I&rsquo;ll share with you my experiences with <em>Blazor WebAssembly<\/em>, the pros, the cons, the whatnot.<\/p>\n<blockquote>\n<p><strong>TL;DR;<\/strong> If you&rsquo;re not already a fluent <em>ASP.NET<\/em> developer, I&rsquo;m not sure that you want to use it. If you are, then maybe <em>Blazor<\/em> might be an interesting choice.<\/p>\n<\/blockquote>","category":["WASM","Blazor","CSharp","AspNetCore","Front-end"]}}}