Thoughts on .Net & Coding

In the previous part of this multipart article series we implemented JWT authentication in CRUD minimal APIs. Recollect that we are using a hard-coded user name and password while issuing the token in the getToken handler function. Wouldn't it be nice if we integrate ASP.NET Core Identity into app so that membership features such as account creation and user validations are taken care of easily? That's the agenda for this part of the article.

In the previous part of this article series we learned to integrate Swagger with ASP.NET Core minimal APIs. So far we created minimal APIs for performing CRUD operations. Now it's time to add authentication and authorization to the minimal APIs. As with controller based APIs the most common approach to implement authentication in minimal APIs is to use JSON Web Token or JWT. To that end this part of this series will cover that and will also tweak Swagger configuration to use JWT while invoking the minimal APIs.

In the previous part of this article series we developed minimal APIs for performing CRUD operations on the Employees table. Once you build the minimal APIs, you typically want to test them by invoking their endpoints. The best way to do so is by building a client application using HttpClient or JavaScript. However, creating such a client can be time consuming. You might want to quickly test the minimal APIs before moving ahead with your development. That's where Swagger can be helpful. In this article we will integrate Swagger support into the minimal APIs and test the CRUD operations.

One of the features of ASP.NET Core 6 that has got much attention is minimal APIs. You can now create API endpoints without creating a controller and routing related configuration. I have already discussed creation of minimal APIs in a few articles published earlier. The earlier articles were published during the Preview days of ASP.NET Core 6 and use Visual Studio 2019. Now that the final versions of ASP.NET Core 6 and Visual Studio 2022 are available, it's time to revisit the subject and look into various aspects of minimal APIs in more details. To that end this multipart article series is going to discuss just that.

If you are keeping an eye on the progress of ASP.NET Core 6 you are probably aware that .NET 6, C# 10, and Visual Studio 2022 have been released. There are lots of new things, small to big, added to the overall .NET family and I have discussed a few of them in my previous articles. In this article I will show you how to create your first web application in Visual Studio 2022. I assume that you are already familiar with Visual Studio 2019 and ASP.NET Core in general. This is going to be a quick introduction to give you a feel of the new IDE and project structure.

In the Part 1 of this article you learned to implement drag-n-drop in a Blazor Server application. So far we are able to drag-n-drop files on to a drop target and list those file names in the fileBasket. However, no files are actually sent to the server. That's what we will do in this part of the article. Although our focus is going to be minimal API approach, we will explorer three variations of the process.

Uploading files from client computer to the server is a common task in web applications. You can either use jQuery Ajax or Blazor's InputFile component to accomplish that task. Files to be uploaded on the server are typically selected by the end user using file input field. However, most of the browsers also allow you to select files by dragging them from the client computer to your web application. To that end this article discusses how drag-n-drop of files can be done in Blazor Server apps. I am going to assume that you are familiar with Blazor's JavaScript interop. You may read my previous article in case you aren't familiar with Blazor's JS interop.

ASP.NET Core Blazor allows you build SPAs using C#, HTML, and CSS. Although you can develop Blazor apps without using any JavaScript, at times you might want to invoke some JavaScript code from your Blazor components. Moreover, the JavaScript code might also want to invoke some C# methods. To that end this article quickly illustrates how this can be accomplished using Blazor's JavaScript interop features.