Guide .NET data access with Entity Framework Core and Dapper best practices.
npx skills add https://github.com/Objective-Arts/lens --skill dotnet-data
Please help me install this Agent Skill. Skill: dotnet-data Source: https://github.com/Objective-Arts/lens/tree/main/canon/csharp/dotnet-data Command: npx skills add https://github.com/Objective-Arts/lens --skill dotnet-data
This Skill addresses common pitfalls and best practices in .NET data access using Entity Framework Core and Dapper, ensuring efficient, maintainable, and performant data operations.
AsNoTracking and projections, while complex order reporting leverages Dapper for speed.Use the dotnet-data skill to review the best practices for DbContext lifetime management in a .NET application.
High-intent search queries and answers about installing and using this skill.
Optimize EF Core queries by applying AsNoTracking and projections to read-only operations. This prevents unnecessary change tracking overhead, significantly improving performance in high-traffic scenarios like product catalog fetching.
Mitigate the EF Core N+1 problem by using eager loading with Include or projections. This ensures related data is fetched in a single query rather than executing separate queries for each entity, reducing database round trips.
Use Dapper instead of Entity Framework Core for performance-critical read operations and complex reporting. Dapper provides faster raw SQL execution, while EF Core remains better suited for complex CRUD operations and schema management.
Manage database schema migrations safely in .NET by leveraging EF Core migration strategies. This handles database schema evolution systematically, ensuring data access patterns remain synchronized with structural changes without data loss.
You can execute raw SQL safely using Entity Framework Core. The framework provides mechanisms for secure raw SQL execution, allowing you to handle complex reporting or specific queries without exposing the application to SQL injection risks.
Recommended DbContext lifetime management for .NET applications typically uses scoped lifetimes. This ensures context instances are shared within a request, preventing memory leaks and managing concurrent data access operations efficiently.
ronnythedevScaffold a layered .NET solution with Clean Architecture boundaries.
lexicalninjaDesign database schemas, migrations, and data access layers for applications.
MovchanetsDesign scalable backend architectures and API layers for Node.js, Express, and Next.js.
pluginagentmarketplaceGenerates Go database patterns for SQL, ORM, transactions, migrations, and connections.