Why should you care?

ShopNest services should not open SqlConnection everywhere. One ShopNestDbContext per request centralizes configuration, tracking, and transactions.

See it live — copy this example

Paste into a .NET project with EF Core packages, then run with LocalDB/SQL Server (dotnet ef / dotnet run).

public class ShopNestDbContext : DbContext
{
    public ShopNestDbContext(DbContextOptions<ShopNestDbContext> options)
        : base(options) { }

    public DbSet<Product> Products => Set<Product>();
    public DbSet<Order> Orders => Set<Order>();
    public DbSet<Customer> Customers => Set<Customer>();
}

What happened?

• Inheriting DbContext gives you Set() and change tracking.
• The constructor receives options (connection, provider) injected from DI at startup.

Practice next

1. Add ShopNestDbContext to ShopNest.Infrastructure.
2. Register AddDbContext in Program.cs with your LocalDB connection string.
3. Resolve ShopNestDbContext in a minimal API endpoint and call Database.CanConnectAsync().
4. Override OnConfiguring only for design-time fallback — prefer DI options in production.
5. Add DbSet and run dotnet build to see compile-time safety.

Remember

DbContext is the EF session object. DbSet properties map to tables. Register as Scoped in web applications.

ShopNest scoped data session

Checkout controller receives ShopNestDbContext via constructor injection for the duration of one HTTP request.

Outcome: Connection and tracker lifetime align with a single customer action.