Skip to main content

EF Core–.NET 8 update

The .NET 8 release of Entity Framework Core offers a large list of new features. The goal of this post is not to walk you through all these features, therefore you can have a look at the What's new page on Microsoft Learn, instead I want to talk about a specific feature as a follow-up on the previous posts about EF Core I did this week.

In those posts I talked about the FromSql method to use your handwritten SQL statements to fetch EF Core entities. What I didn’t mention is that this only worked for entities that were registered as an entity to the DbContext.

Starting with the EF Core 8 release, this condition has been removed, allowing us to create any SQL statements you want and map them to C# objects.

This means that EF Core can now become an alternative to micro-ORM’s like Dapper. Of course there is maybe still a performance difference(I’ll do a benchmark and share the results) but feature wise this is a great addition.

To use this feature, we need to call the SqlQuery<T> method:

var results = await db
.Database
.SqlQuery<Product>($"SELECT * FROM dbo.Products")
.ToList();
record Product(int ProductID, string ProductName);
view raw GetProducts.cs hosted with ❤ by GitHub

The cool thing is that you can combine this with Linq statements. EF Core will generate a SQL query that combines your handwritten statement with generated SQL:

SELECT "n"."ProductID", "n"."ProductName", "n"."CategoryID"
FROM (
SELECT * FROM dbo.Products
) AS "n"
WHERE "n"."CategoryID" = 1
view raw GetProducts.sql hosted with ❤ by GitHub
var categoryID=1;
var results = await db
.Database
.SqlQuery<Product>($"SELECT * FROM dbo.Products")
.Where(p=> p.CategoryID==1)
.ToList();
record Product(int ProductID, string ProductName, string CategoryID);

More information

What's New in EF Core 8 | Microsoft Learn

SQL Queries - EF Core | Microsoft Learn

Popular posts from this blog

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

.NET 9 - Goodbye sln!

Although the csproj file evolved and simplified a lot over time, the Visual Studio solution file (.sln) remained an ugly file format full of magic GUIDs. With the latest .NET 9 SDK(9.0.200), we finally got an alternative; a new XML-based solution file(.slnx) got introduced in preview. So say goodbye to this ugly sln file: And meet his better looking slnx brother instead: To use this feature we first have to enable it: Go to Tools -> Options -> Environment -> Preview Features Check the checkbox next to Use Solution File Persistence Model Now we can migrate an existing sln file to slnx using the following command: dotnet sln migrate AICalculator.sln .slnx file D:\Projects\Test\AICalculator\AICalculator.slnx generated. Or create a new Visual Studio solution using the slnx format: dotnet new sln --format slnx The template "Solution File" was created successfully. The new format is not yet recognized by VSCode but it does work in Jetbr...