|
Hey Reader, In today’s tutorial, I’ll walk you through how to use Dapper, a high-performance micro ORM (object-relational mapper) with a .NET 8 Web API and SQL Server. We’ll cover everything you need to know to build a simple CRUD (Create, Read, Update, Delete) application. Watch on YouTube 📺Check out the full tutorial on YouTube to see everything in action 👇 What We’ll Be DoingWe’re going to work with a simple video game database to start. You’ll learn how to:
First, we’ll set up our Web API using Visual Studio, configure the project, and add Dapper as a NuGet package. Once everything's set, we’ll create a model for our video games that mirrors the database structure: ID, title, publisher, developer, and release date. Next up, you’ll see how to establish a connection to the SQL Server using a connection string in the Why Dapper?Dapper gives you full control over your SQL queries. While it doesn’t auto-generate queries like Entity Framework, Dapper ensures everything stays efficient and lightweight, making it ideal for high-performance apps. Plus, if you're working in an environment where you're dealing with an existing database or a team that handles the database design, Dapper might be perfect for you! Step-by-Step Guide1. Set up the Project:First, let's create a new ASP.NET Core Web API project in Visual Studio. Make sure to select .NET 8. 2. Install Dapper:In the NuGet Package Manager, search for and install 3. Create a Video Game Model:Add a new folder called 4. Add a Connection String:Next, open the 5. Create a Repository Interface:Add a new folder called 6. Create the Repository Implementation:Now, create a class that implements the First, we inject IConfiguration, so that we get access to the connection string from the appsettings.json file. It is necessary to create a connection to the database each time we want to run a query. We also add a little function to create the connection whenever we need it. Next, we implement all the CRUD operations. Let's start with the easy one, receiving all video games. Let's also create the VideoGamesController and add the corresponding GET method there. Last step is registering the repository in the Program.cs. Now we can run the application and test the first call with Swagger. Awesome! Now, let's continue with the other CRUD operations - receiving a single video game, adding a video game, updating and deleting one. Please note, that we're using parameters here. Otherwise, we would risk SQL injection attacks. Don't forget the corresponding controller methods. Wrapping UpNow you have a fully functional API that can interact with a SQL Server database using Dapper. You understand how to fetch data from the database, add new records, update existing ones, and delete records you no longer need. What's your experience with Dapper? Is it your goto tool in your projects or would you rather use Entity Framework or something else? Happy coding and have an awesome weekend! Take care, Patrick PS: Need help understanding .NET & Blazor? There are two ways I can help you with:
PPS: Would you like to sponsor this newsletter? Click here. 💌 |
Become a .NET & Blazor expert with weekly tutorials featuring best practices and the latest improvements, right in your inbox.
Hey friend,A few weeks ago, I was on a live call with a group of .NET developers. No agenda. No slides. Just real developers talking honestly about what is actually working with AI tools right now - and what is not. One of the first things Paul said set the tone for the whole session: "In the hands of an experienced developer, any AI tool is an accelerator. In the hands of a rookie, it's just dangerous." I keep thinking about that line. Because I think it is exactly right - but it also misses...
Hey friend, This week, I built a working Blazor app from scratch in about 30 minutes. But that's not really the point. The point is how. Not by throwing a prompt at Claude and hoping for the best. But by thinking about architecture first, defining instructions and skills for the AI upfront, and then letting it implement while you stay in control and review the output. That's the difference between AI doing your job and AI doing the boring parts of your job. The video walks through exactly...
Hey friend, A year ago, I said AI coding tools weren't the future. I want to correct that. The distinction I missed: there's a real difference between vibe coding (copy-paste until it compiles, no understanding required) and skilled AI-assisted development (you own the architecture, AI implements it, you review the output). I was criticizing the first and accidentally dismissing the second. In 2026, skilled AI-assisted development is the professional standard. Not using these tools is now a...