Ali Hamza Ansari
Ali Hamza Ansari @AliHamzaAnsar16 ·
🚫Stop defaulting to the Repository Pattern in EF Core. DbContext already acts as Repository + Unit of Work. Adding extra layers can mean more boilerplate, less flexibility, more complexity. Know when to keep it simple. Read more:blog.elmah.io/when-not-to-us…O #dotnet #efcore
When NOT to use the repository pattern in EF Core

Stop using the repository pattern as a default. Learn when EF Core's DbContext is enough and why abstractions can sometimes overengineer apps.

From blog.elmah.io
7
ZZZ Projects
ZZZ Projects @zzzprojects ·
New article on YogiHosting! Learn how to boost your EF Core performance using Entity Framework Extensions for fast bulk operations (insert, update, delete, merge). 👉yogihosting.com/entity-framewo…O #DotNet #EFCore #EntityFramework #Performance #ZZZProjects
The Entity Framework Extensions: Performance-Focused (Need for Speed) when working with large...

Working with large datasets over the standard Entity Framework Core SaveChanges() method can quickly become a performance bottleneck. The reason is due to the SaveChanges() method’s “one-by-one”...

From yogihosting.com
11
Jean-François Meyers
Jean-François Meyers @meyersjf ·
🚫 Ne retournez jamais vos entités EF Core depuis une API. Fuites de données, références circulaires, N+1 & couplage au schéma ne sont pas des bugs, mais des conséquences. ✅ Responses explicites = contrat stable & API plus sûre. �granit-fx.dev/blog/never-ret…5x #EFcore #Dotnet
Never Return Your EF Entities From an API

Returning EF Core entities directly from your endpoints leaks internal structure, creates circular references, and exposes sensitive data. Use response records instead.

From granit-fx.dev
13
Jean-François Meyers
Jean-François Meyers @meyersjf ·
🚫 Never return your EF Core entities from an API. Data leaks, circular refs, N+1 queries & schema coupling are not bugs - they’re consequences. ✅ Use explicit Response records. Stable contract, safer APIs. �granit-fx.dev/blog/never-ret…5x #EFCore #Dotnet
Never Return Your EF Entities From an API

Returning EF Core entities directly from your endpoints leaks internal structure, creates circular references, and exposes sensitive data. Use response records instead.

From granit-fx.dev
20
Srinivasan J | .NET
Srinivasan J | .NET @rjsrinivasan ·
EF Core 10 + SQL Server 2025 now supports native Vector Search 🔍 Search by meaning, not just keywords - right inside your existing DbContext. No separate vector DB needed. Just .NET patterns you already know. #dotnet #efcore #sqlserver #aic
35
.Net University
.Net University @dotnetES ·
Si usas EF y SQL Server puedes ahorrar espacio con columnas SPARSE Desde .NET 6 / EF Core 6 puedes configurarlas fácilmente con IsSparse() en OnModelCreating Ideal para propiedades con muchos valores NULL. Para saber mas entra a : NETUniversity.org #dotnet #efcore
95
.Net University
.Net University @dotnetES ·
💡¿Cuántas veces has repetido el mismo .Where() en distintos servicios? Con Specification Pattern puedes reutilizar filtros, centralizar reglas y testear en memoria sin DB ni mocks Más limpio, más mantenible y más expresivo en .NET #dotnet #csharp #efcorev
106