Thoughts on .Net & Coding

If you are tracking the progress of ASP.NET Core 6, you are probably aware of the new features being introduced. One of the new and interesting features of ASP.NET Core 6 is the new way of configuring web application startup in just a few lines of code. Currently this new way of application startup has been introduced in empty project templates but you can easily use it in any other project template (say, ASP.NET Core MVC or Razor Pages). To that end this article shows you how standard ASP.NET Core MVC project template generated code can be modified to use the new way of application startup.

In Part 1 of this article, you learned to setup a Blazor Server app using ASP.NET Core's empty project template. Continuing further, this part teaches you to prepare a Blazor WebAssembly app using an empty project template. Since you are familiar with the basics outlined in the previous part, let's get going by creating a new empty project in Visual Studio. 

Visual Studio offers Blazor Server and Blazor WebAssembly project templates to the ASP.NET Core developers. Most of the times beginners are taught to utilize these default project templates to build the respective Blazor apps. However, it would be an interesting exercise for beginners to setup Blazor Server and Blazor WebAssembly projects using ASP.NET Core's Empty project template. In this two part article you will develop Blazor "Hello World" application using the Empty project template.

ASP.NET Core developers often store styling information for MVC views, Razor Pages, and Razor Components into a style sheet file. The style sheet is then applied to various pages using HTML element. Although this works great in many cases, at times you might want to isolate view / page / component specific styling information into its own CSS file. Luckily, MVC views, Razor Pages, and Razor Components support such CSS isolation. This article explains how.

In Part 5 of this series you created three partials namely _ShowTeam, _InsertTeam, and _UpdateTeam. In this part you will add the remaining three partials viz. _ShowTeamMember, _InsertTeamMember, and _UpdateTeamMember. For your quick reference let's take a look at the organization of partials again:

In Part 4 of this article series we added the Main view, _Teams partial, and _TeamMembers partial. Recollect that _Teams partial and _TeamMembers partial show a Team or TeamMember record in read-only, insert, or update mode. This is done with the help of six partials - three belonging to _Teams partial and three belonging to _TeamMembers partial.

In Part 2 and Part 3 of this article series we completed TeamsComtroller and TeamMembersController respectively. All of the controller actions that we wrote so far return Main view. They also supply a MasterDetailViewModel object to the Main view. In this part we will begin developing a set of views and partials that renders the UI of the application.

In the previous part of this article series you created the TeamsController that performs CRUD operations on the Teams table. In this part you will continue to develop the app by creating TeamMembersController. The TeamMembersController performs CRUD operations on the TeamMembers table. Begin by adding TeamMembersController class into the Controllers folder. The following figure shows both the controllers in the Controllers folder.