在我的情况下，我发现在myContext.SaveChangesAsync()调用之前缺少“await”语句。在这些异步调用之前添加await，为我解决了数据读取器的问题。

It is not about closing connection. EF manages connection correctly. My understanding of this problem is that there are multiple data retrieval commands executed on single connection (or single command with multiple selects) while next DataReader is executed before first one has completed the reading. The only way to avoid the exception is to allow multiple nested DataReaders = turn on MultipleActiveResultSets. Another scenario when this always happens is when you iterate through result of the query (IQueryable) and you will trigger lazy loading for loaded entity inside the iteration.

这个问题可以简单地通过将数据转换为列表来解决

 var details = _webcontext.products.ToList();


            if (details != null)
            {
                Parallel.ForEach(details, x =>
                {
                    Products obj = new Products();
                    obj.slno = x.slno;
                    obj.ProductName = x.ProductName;
                    obj.Price = Convert.ToInt32(x.Price);
                    li.Add(obj);

                });
                return li;
            }

在第二次查询之前，我使用以下代码段解决了这个问题:

 ...first query
 while (_dbContext.Connection.State != System.Data.ConnectionState.Closed)
 {
     System.Threading.Thread.Sleep(500);
 }
 ...second query

您可以以毫秒为单位更改睡眠时间

P.D.在使用线程时很有用

在我的情况下，我发现在myContext.SaveChangesAsync()调用之前缺少“await”语句。在这些异步调用之前添加await，为我解决了数据读取器的问题。

还有另一种方法可以解决这个问题。这是否是一种更好的方式取决于你的情况。

这个问题是由惰性加载导致的，所以避免它的一种方法是不要有惰性加载，通过使用Include:

var results = myContext.Customers
    .Include(x => x.Orders)
    .Include(x => x.Addresses)
    .Include(x => x.PaymentMethods);

如果使用适当的Includes，就可以避免启用MARS。但是如果你错过了一个，你就会得到错误，所以启用MARS可能是最简单的修复方法。