Thoughts on .Net & Coding

In the previous article we used SqlDataReader to execute SELECT queries and to read data from the database. You often need to execute action queries - INSERT, UPDATE, and DELETE - on the database to perform the respective operations. As far as as SQL Server data provider is concerned you can do that with the help of SqlCommand object. That's what we are going to discuss in this article.

In the previous article we learned the basics of the ADO.NET data provider for SQL Server. We also took a glance at the SQL Server data provider's object model. Now it's time to put those objects to use in a simple CRUD web application. To that end this article kicks off the development by creating a simple repository for performing the CRUD operations.

At times you may want to skip using EF Core and delve into the underlying data provider yourself. It would be helpful for beginners to understand how EF Core might be working behind the curtains of easy to use ORM. To that end this article gives you a brief overview of the ADO.NET data provider for SQL Server.

In the previous article you learned to use Entity Framework Core InMemory provider to store and retrieve your application data for testing and demoing purposes. An alternative (and a recommended option) is to use SQLite database in in-memory mode. To that end this article discusses just that.

Most of the production cases call for storing data in some physical data store such as a SQL Server database. However, for testing and demoing purposes you may want to store data in memory rather than persistent store. That's where Entity Framework Core InMemory provider can be helpful. In this article we will examine the usage of the EF Core InMemory provider in an ASP.NET Core Razor Pages application.

In the previous part of this article series you developed ListTeamMembers.razor component. Now you need to develop the remaining components namely ShowTeamMember.razor, InsertTeamMember.razor, and UpdateTeamMember.razor. You have already these empty component files in the Shared > TeamMembers folder. The UI rendered by the ShowTeamMember component is shown below.

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.