Blazor sounds like a good starting point, but it is not yet ready to do real world work.
I must admit, I had not looked at Blazor until now because I had been told "it is just a toy, an experiment". After looking at it, I feel that it has the potential to be the basis of something transformational. You can see more of the story at: http://blog.stevensanderson.com/2017/11/05/blazor-on-mono/ Which has a link to a video of his demo app from NDC Oslo: https://www.youtube.com/watch?v=MiLAE6HMr10&feature=youtu.be&t=31m45s which is seriously worth watching! Then reading: https://github.com/SteveSanderson/Blazor "An experimental web UI framework using C#/Razor and HTML, running client-side via WebAssembly The arrival of WebAssembly creates the possibility of building client-side web applications using languages and runtimes that are more typically used for native app development. Blazor runs .NET code in the browser via the Mono runtime, which itself is compiled to WebAssembly and asm.js. The programming model will be familiar to anyone who's worked with Razor (the C#/HTML page format used by ASP.NET MVC and ASP.NET Pages)." Which all looks really promising, until you read… Can I build a real production app with this? No. It's very incomplete. There isn't yet any support for producing optimised production builds or connecting a debugger. Why isn't there an issue tracker? How do I file issues? You don't file issues. There's no support for this. It's experimental. This is all bleeding edge stuff, that blog post is from 5-Nov I will wait a little longer before making any bets on this... But I repeat... I feel that Blazor has the potential to be the basis of something transformational!
