Why should you care?

Some ShopNest report developers prefer SQL-like query syntax for readability in complex joins — both styles compile identically.

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).

var q =
    from p in _context.Products
    where p.CategoryId == categoryId && p.IsPublished
    orderby p.Price descending
    select new { p.Id, p.Name, p.Price };

var items = await q.Take(20).ToListAsync();

What happened?

• from/where/orderby/select desugar to Where, OrderByDescending, Select methods.
• EF sees method syntax and generates TOP 20 SELECT with filters.

Practice next

1. Rewrite one method-syntax query as query syntax.
2. Use join clause for Order–Customer report.
3. Confirm ToQueryString identical for equivalent queries.
4. Convert group by query syntax from sales report lesson to method syntax.
5. Add let clause for intermediate calculated discount field.

Remember

Query syntax is sugar over method syntax. EF translates both to the same SQL. Use whichever reads clearer for the team.

ShopNest category listing

Junior dev writes query syntax for category product list — senior reviews ToQueryString output.

Outcome: Readable LINQ with verified efficient SQL plan.