# Blazor et al

I've been developing since before [.NET](https://dotnet.microsoft.com/en-us/) existed and ever since its first appearance I've not really been interested in looking elsewhere.

My weapons of choice are [Visual Studio](https://visualstudio.microsoft.com/) and [C#](https://docs.microsoft.com/en-us/dotnet/csharp/) and I've built up extensive use of [SQL](https://www.w3schools.com/sql/) and [XML](https://www.w3schools.com/xml/) along the way. [HTML](https://www.w3schools.com/html/) and [CSS](https://www.w3schools.com/css/) are unavoidable and I dislike [JavaScript](https://www.w3schools.com/js/). [TypeScript](https://www.typescriptlang.org/) is an acceptable middle ground between JavaScript and C# but I'd much rather just be able to use C# throughout, hence my interest in [Blazor](https://dotnet.microsoft.com/en-us/apps/aspnet/web-apps/blazor).

When Blazor first entered the fray it caught my attention, but alas not the attention of my employer. Times change, I've moved on after 21 years with that employer and Blazor is still calling to me, so I hope to share with you some of what I learn on my own journey to learn Blazor from the very beginning.

On the way, I expect to digress into all things .NET/C#, such as [ASP.NET Web API](https://docs.microsoft.com/en-us/aspnet/core/web-api/?view=aspnetcore-6.0) ([Open API](https://www.openapis.org/), [REST](https://dotnet.microsoft.com/en-us/apps/aspnet/apis), [gRPC](https://docs.microsoft.com/en-us/aspnet/core/grpc/?view=aspnetcore-6.0), [Entity Framework](https://docs.microsoft.com/en-us/ef/), SQL/NoSQL, some favourite [patterns](https://www.c-sharpcorner.com/UploadFile/bd5be5/design-patterns-in-net/), [Azure DevOps](https://azure.microsoft.com/en-us/services/devops/) and anything else that catches my eye.