Skip to main content

Entity Framework error: There is already an open DataReader associated with this Command which must be closed first

On a recent project I started to use Entity Framework. So far the experience has been good, but sometimes I get some unexpected issues(and I have to force myself to not go back to NHibernate Glimlach).

Let’s have a look at the code first:

public class DemoContext:DbContext
{
public DbSet<Category> Categories
{
get;
set;
}
}
view raw DemoContext.cs hosted with ❤ by GitHub
var context=new DemoContext();
var categories=context.Categories;
foreach (var category in categories)
{
Debug.WriteLine(category.Products.Count.ToString());
}
view raw Sample.cs hosted with ❤ by GitHub

I think there’s nothing special about this code. I first load all the categories and then walk through all the products(which will cause a n+1 issue, but that’s another discussion). When I first ran this code it failed with the following error message:

"An error occurred while executing the command definition. See the inner exception for details."

When I drilled down to the innermost exception, the following message was shown:

"There is already an open DataReader associated with this Command which must be closed first."

  To solve this, you have to add an extra part to your connection string:

Data Source=srv01;Initial Catalog=Northwind;Persist Security Info=True;Integrated Security=True;MultipleActiveResultSets=true

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