Why should you care?

ShopNest's catalog API would drown in hand-written INSERT and SELECT strings. EF Core keeps product and order logic in typed C# that refactors safely when columns change.

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 Product
{
    public int Id { get; set; }
    public string Name { get; set; } = "";
    public decimal Price { get; set; }
}

// Later with DbContext:
// await _context.Products.AddAsync(new Product { Name = "Desk Lamp", Price = 1299 });
// await _context.SaveChangesAsync();

What happened?

• Product is a plain class EF will map to a Products table.
• AddAsync stages a row; SaveChangesAsync sends INSERT SQL — you never wrote the SQL string yourself.

Practice next

1. Install .NET 8 SDK and create ShopNest.Domain as a class library.
2. Add the Product class above and run dotnet build.
3. Sketch how Id, Name, and Price become SQL columns on paper.
4. Add a StockQty int property and predict the migration column type.
5. Rename Name to Title locally and list what breaks before you run dotnet build.

Remember

EF Core maps C# classes to relational tables. SaveChangesAsync commits staged changes as SQL. ShopNest.Data builds on this pattern throughout the course.

ShopNest product catalog bootstrap

A new Flipkart-style squad starts ShopNest.Data with Product as the first entity before any API endpoints exist.

Outcome: Schema and C# model stay in one Git repo instead of drifting SQL scripts.