Thoughts on .Net & Coding

In the previous article we created a custom validation attribute to validate Blazor's EditForm. If you developed ASP.NET Core MVC apps before, you might have used FlientValidation library for validation instead of using validation attributes. Can we use FluentValidation in Blazor?

Validating form data is one of the most common task in any web application. ASP.NET Core offers a set of validation attributes for performing model level data validations. Blazor apps can also make use of the same validation attributes. Some of the validation attributes include [Required], [StringLength], [Range], and [Compare]. At times you want to perform some validation not covered by these attributes. This is when you want to create a custom validation attribute. In this article we will discuss how that can be done.

A few years ago I wrote an article describing how ASP.NET Core DI container behaves when multiple implementations of an interface are registered. It's time to revisit the concept because .NET 8 has something better to offer -- Keyed Services. I am going to use the same example that I used in the earlier article. We will modify the example for .NET 8.

In the previous article you learned to deploy an ASP.NET Cor web app in an Azure App Service using two techniques. Recollect that we are storing the database connection string in the appsettings.json file. And we need to change it to match the production setup at the time of deployment. In this article we will discuss two better ways of storing the database connection string. Firstly, we will learn to store the connection string into the Azure App Service itself. And then we will store it in Azure Key Vault.

No matter how carefully you design your web pages and components there is always a possibility that your application throws an error at runtime. To trap and handle such unforeseen circumstances you can use IExceptionHandler interface introduced in ASP.NET Core 8.

https://www.binaryintellect.net/articles/3f87c933-2e21-4df4-9c26-8f350afc68da.aspx

In the previous part of this series we wired token based authentication and Identity API endpoints into our Employees Web API. Now it's time to test and confirm the working of our API.

If you are following previous articles of this series, you are probably comfortable working with Web API and class library projects in VS Code. We will take our example a step further and add authentication to the Web API.

In the previous article you learned to setup Visual Studio Code for ASP.NET Core development. We created ASP.NET Core MVC project and used scaffolding to create CRUD pages. In this article you will create a Web API that exposes the CRUD functionality to its client apps. You will also wrap the EF Core code inside a class library project.