So, how does it all work? Blazor takes advantage of WebAssembly technology that allows serving binaries directly to the browser. The base technology itself is standardised and has been made available on Chrome, Edge, Firefox, and WebKit browser engines. So, it covers all the major browsers with the exception of the ones that aren't very widely used. The only problem with this is that it's not fully compatible with Internet Explorer, which some stubborn enterprises insist on using until it fully goes out of support. Employees of such organisations are the only users that will not be able to use WebAssembly, which implies that they will not be able to take full advantage of Blazor. Although Blazor can be run on older browsers that don't have access to WebAssembly, it can only do so by relying on asm.js, which is significantly slower than WebAssembly and only works if additional polyfill is applied.
Blazor apps are built in the same way as any other ASP.NET app is built. Developers experienced with MVC will find it particularly easy to adjust. The latest preview of Visual Studio, 15.7, already has project templates for this types of project. However, as it is only available in a preview version, it currently has some limitations. For example, you have to keep stopping and starting the entire solution for any of your changes to take effect. But the framework is being actively worked on, so we should be seeing the full production-ready version of it at some point in the near future.
For more information, follow this link:
Published by Mobile Tech Tracker
Posted on 18 Apr 2018
FBlondel 14 May 2018
Concerning compatibilty, It will be supported on Internet Explorer 11, see for example this topic: https://github.com/aspnet/Blazor/issues/789
Fiodar Sazanavets (Admin) 15 May 2018
Thank you for pointing this out. The article has been corrected accordingly