Thoughts on .Net & Coding

In the preceding part of this article series you created master CRUD components namely ListTeams, ShowTeam, InsertTeam, and UpdateTeam. Continuing your development you will complete the detail CRUD components in this part. By the end of this part you will be able to see master-detail behavior and CRUD operations in action. So, let's get started with the detail components.

In the previous part of this article series you developed the List component that displays a list of Teams in a table. In this part you will create ShowTeam, InsertTeam, and UpdateTeam components to perform the CRUD operations on the Teams table. The following figure shows how the ShowTeam component displays a Team in the browser.

In the previous part of this series you were introduced to the UI and overall functioning of the master-detail Blazor Server app. You also created Team and TeamMembers tables and EF Core model. You have already created the Blazor Server project. Now it's time to kick start the component development. To build the master detail UI you could have but all the markup and the code in a single Razor component.

Modern applications often prefer to use rich client side frameworks over traditional server side processing. ASP.NET Core provides Blazor (Server and WebAssembly) as a framework for building rich client side web apps. It would be interesting to see how the master detail user interface can be built using Blazor. To that end this multipart article series is going to show you in detail how Blazor Server can be put to use for developing master detail pages.

In the previous part of this multipart article series we migrated the minimal APIs to API controller in order to understand the efforts involved in the process. So far we have learned various aspects of creating minimal APIs. Now let's learn to create client applications that consume the minimal APIs. 

On 13 February 2022 .NET is completing its strong presence of 20 years. Microsoft and developer community is all set to celebrate this occasion in variety of ways. You can read more about their plans here. You can also take a look at what others are doing on Twitter here.

In the previous part of this article series we discussed a few ways of organizing minimal APIs. There can be situations when you would want to migrate your minimal APIs to controller based APIs. In this article we will move our minimal APIs to controller based APIs and see how much work is involved.

In the previous part of this article series you learned to add minimal APIs to the Startup class. So far we have added minimal APIs to the Program.cs file. If you have only a handful of APIs this won't create any problem. But if you have a lots of minimal APIs to deal with, at some point you will want to organize them in a better way.