ASP.NET Core Blazor - A Complete Overview

This is going to be a bit of a rant, but I really don't think anyone should care too much about Blazor until Microsoft proves that they are willing to actually finish and support it.

We're mostly a Typescript shop these days, not because it's a good language or because I'd advice you to ever go full Typescript, but because I currently work in non-SWE related enterprise and our development team is around 4-6 people, depending on the day of the week. In that sort of setup it just helps immensely to have everyone working within the same toolchain, and until Rust and it's Yew actually becomes as productive for building things as React, that means Typescript.

Anyway, we wanted to build an Odata back-end to replace some of the Sharepoint "application" that made sense when the company was growing, but no longer do. Having already had to write a full Odata client for Typescript because all the ones out there weren't good, we didn't really want to dig too much into the server side of it. So naturally that left us with C#, well or Java, but none of us have worked with Java since the dark ages, so it left us with C#.

Having spent time with the following:

  • Asp.Versioning;

  • Microsoft.AspNetCore.Mvc;

  • Microsoft.AspNetCore.OData.Query;

  • Microsoft.AspNetCore.OData.Deltas;

  • Microsoft.EntityFrameworkCore;

I have a love hate relationship with Microsoft tools and their half-finished projects of which Blazor is another example. Everything is great on the surface, but as soon as you dig deeper than what you'll see in these articles, you'll find that the documentation is a bunch of github repositories with sparringly comments, no testing, only "in-memory" workloads and .Net code that has, but hasn't really been, updated to work the way .Net 7 wants you to write C#.

The love in the relationship is that it's really very good when it works, the hate is that it's just terrible to get there.

/r/programming Thread Link -