Tag

#entity-framework

128 posts69 followers

Explore Hashnode

Alternatives

qodors4d ago · 7 min read

C# Concepts Every .NET Backend Developer Should Know in 2026

A .NET API can feel perfectly fine with a little traffic and then start struggling as the app grows. Queries get slower, outgoing HTTP calls hold on to threads, and tightly coupled services make every

qodors.hashnode.dev

spipaliya8Oct 1 · 8 min read

IQueryable vs IEnumerable in C#: Key Differences

When working with collections in C#, you will often come across two important interfaces: IEnumerable<T> IQueryable<T> They may look similar because both allow you to query collections using LINQ.

sudhirpipaliya.hashnode.dev

spipaliya8Sep 19 · 17 min read

EF Core Projection: How Select Can Improve Query Performance

When working with Entity Framework Core, one of the easiest ways to accidentally retrieve more data than necessary is to load complete entities. For example: var students = await context.Students

sudhirpipaliya.hashnode.dev

spipaliya8Sep 14 · 13 min read

EF Core Include vs Select: Which One Should You Use?

When working with Entity Framework Core, developers often use Include() to load related data. But there is another powerful approach: Select() So which one should you use? The answer depends on what

sudhirpipaliya.hashnode.dev

spipaliya8Sep 7 · 12 min read

EF Core Query Splitting vs Single Query: Which One Should You Use?

Entity Framework Core makes it very easy to load related data using Include() and ThenInclude(). For example: var students = await context.Students .Include(x => x.Standard) .Include(x => x.Di

sudhirpipaliya.hashnode.dev

spipaliya8Sep 2 · 9 min read

Why Database Indexes Matter for EF Core Performance

Entity Framework Core makes it easy to query data using LINQ. But even a well-written EF Core query can become slow when your database grows. One of the most important factors behind query performance

sudhirpipaliya.hashnode.dev

Patrick KearnsSep 1 · 13 min read

When AsNoTracking Makes EF Core Slower

There is a piece of EF Core advice that appears in almost every performance discussion: If the query is read-only, use AsNoTracking(). Its usually good advice. Tracking entities requires EF Core to

1 fullstackcity.com

Coding DropletsAug 4 · 12 min read

Unable to Create an Object of Type DbContext in EF Core: Causes and Fixes

You add an entity, run dotnet ef migrations add AddOrders, and the tooling stops dead: Unable to create an object of type 'AppDbContext'. For the different patterns supported at design time, see https

codingdroplets.com

Eugene AtinbireJul 28 · 4 min read

How I Reduced Build Time from Over 5 Minutes to Under 30 Seconds by Consolidating 400+ Entity Framework Migrations

As developers, we often focus on optimizing application performance for our users, but we sometimes overlook something just as important our own developer experience. In our case, one of the biggest p

ayinenongre.hashnode.dev

qodorsJul 25 · 5 min read

The N+1 Query Problem in EF Core (And How to Spot It Before Production Does)

A page that felt fine in testing is slow in production. Same code, same query, but now it crawls. You open the SQL log and there it is — not one query, but two hundred. One to load the list, then one

qodors.hashnode.dev

Search Hashnode

Explore Hashnode

Trending tags this week

C# Concepts Every .NET Backend Developer Should Know in 2026

IQueryable vs IEnumerable in C#: Key Differences

EF Core Projection: How Select Can Improve Query Performance

EF Core Include vs Select: Which One Should You Use?

EF Core Query Splitting vs Single Query: Which One Should You Use?

Why Database Indexes Matter for EF Core Performance

When AsNoTracking Makes EF Core Slower

Unable to Create an Object of Type DbContext in EF Core: Causes and Fixes

How I Reduced Build Time from Over 5 Minutes to Under 30 Seconds by Consolidating 400+ Entity Framework Migrations

The N+1 Query Problem in EF Core (And How to Spot It Before Production Does)