|
Hey Reader, Today, I'd like to show you two powerful tools for managing data in .NET projects: Entity Framework and Dapper. I'm sure you already heard about them. First, let me explain what an ORM is and then walk you through examples of CRUD (Create, Read, Update, Delete) operations using both tools. Watch on YouTube ๐บCheck out the full tutorial on YouTube to see everything in action ๐ What is an ORM?An ORM (Object-Relational Mapper) is a tool that helps your application communicate with a database. Instead of writing complex SQL queries, an ORM allows you to work with database data as if it were just regular objects in your programming language. This makes it easier to manage data, as you don't need to write as much SQL code. It's like a translator that turns your code into commands that the database can understand. CRUD Operations with Entity FrameworkEntity Framework (EF/EF Core) is a comprehensive ORM developed by Microsoft. It handles data management tasks like querying, saving, and updating with minimal manual SQL. Let's see how to perform CRUD operations with EF: 1. CreateTo add a new video game character to the database: Here, we create a new 2. ReadTo retrieve a character's details: We use 3. UpdateTo update a character's weapon: After finding the character, we change its 4. DeleteTo remove a character from the database: We locate the character, remove it from the context, and then save the changes to delete it from the database. CRUD Operations with DapperDapper is a lightweight and fast micro-ORM that requires more manual SQL coding. It provides fine-grained control over SQL operations, making it ideal for performance-critical applications. 1. CreateTo add a new game character: We use a SQL 2. ReadTo fetch a character's details: We use a SQL 3. UpdateTo update a character's weapon: The SQL 4. DeleteTo remove a character: We use a SQL ConclusionEntity Framework is perfect for projects where you want a comprehensive solution that handles a lot of the database management work for you, while Dapper provides greater control and efficiency, ideal for performance-critical tasks. Both tools have their strengths, and the best choice depends on your specific needs and comfort level with SQL. Try implementing these examples in your projects to see which one fits your workflow best. What's your experience so far with Entity Framework and Dapper? I promise I'll read your reply! ๐ 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, I don't really write code by hand anymore. I describe what I want, and the AI builds it. For a while, that scared me. If I am not writing the code, does everything I spent years learning still matter? Does my stack matter at all? If you are a developer right now, I would bet you have felt some version of that too. Here is where I landed. It flipped the whole thing for me. The other day I was debugging a slow app, talking it through with the AI. Would WebAssembly help here? Is it...
Hey friend, Lately I told an AI Iโd see it in 7 hours, and went to bed. It was done in 2. Across two different projects. Thereโs this thing people call the night shift. You give an AI agent a pile of work, start it in a loop, and go to sleep while it keeps working on your real codebase. I tried it a month ago and could not make it work, the model just fell apart. But with the newest models, it works now. And the surprising part wasnโt that it ran all night. Itโs that it ran out of work before...
Hey friend, For almost every .NET project I start now, I reach for the same architecture. Not clean architecture. Not the classic controller, service, repository stack that pretty much every tutorial taught us a decade ago, me included... I reach for vertical slice architecture. In my latest video, I break down exactly what it is, why it became my default, and the part almost nobody is talking about. Now that we are all building alongside AI, the rules for choosing an architecture have...