Async loads, related data and performance

Data Binding with EF CoreModule 6The lesson guide, the walkthrough video, the knowledge check and the hands-on lab this sample was built from are on learnwisej.com — free, with an AI tutor in every lesson.

Open the course

This example is the ticket browser with EF Core logging on in Development, the grid query as a no-tracking projection with paging of 50 in SQL, and the editor's related data loaded deliberately (the last five comments by a filtered no-tracking read, the full history by explicit loading on demand). The naive branch the lab starts from is kept in TicketQueryService.SearchTicketsNaiveAsync as the measured baseline for the tests and the lab notes.

The source of this sample

iceteagroup/LearnWisej-SamplesData Binding with EF Core Course/Module 6

Browse this folder on GitHub

Or clone it: git clone https://github.com/iceteagroup/LearnWisej-Samples.git — then open SupportDesk.slnx in Visual Studio and press F5.

Run it

cd "LearnWisej-Samples/Data Binding with EF Core Course/Module 6/SupportDesk.Web"
dotnet run -f net10.0 --urls http://localhost:5406

In Development every EF Core command is written to the console with an [EF] prefix (LogTo), with its SQL and elapsed time. Tests: dotnet test SupportDesk.Tests (TicketPerformanceTests compares the two branches).

What to try

• Search / Next / Previous: the console shows two statements per page of 50, a COUNT and one SELECT that joins the customer, agent and category names. The grid shows Number, Title, Customer, Agent, Category, Status, Due and Updated. Search, Next and Previous are disabled while a page loads.
• Empty result, failed query: No tickets match these filters; a failure shows a friendly AlertBox.
• Edit Ticket: the comments list shows the last five comments; Show full history loads them all.