|
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,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...