Apps for C# and .NETs
.NET application workloads extend C# beyond the web. Desktop apps use WPF or Windows Forms, cross-platform mobile and desktop apps use .NET MAUI, and cloud workloads include containers, Azure services and background workers hosted in the generic host. Entity Framework Core often provides data access across these app types.
Stage: Workloads · Part of the C# and .NET roadmap · Last reviewed 19 November 2026
What to learn in Apps
- Build a simple desktop window with data binding
- Run a long-lived background service with the generic host
- Query a database using Entity Framework Core and LINQ
- Containerise a .NET app with a Dockerfile
- Choose an application model for a given product need
Apps interview questions
What does Entity Framework Core do?
It is an object-relational mapper that maps C# classes to database tables, translates LINQ queries to SQL, tracks changes to objects and saves them back. Migrations evolve the schema alongside the model, reducing hand-written data access code.
What is a BackgroundService in .NET?
It is a base class for long-running work hosted inside the app, such as processing a queue on a schedule. You override ExecuteAsync, and the host starts it with the application and signals a cancellation token on shutdown.
Where Apps fits in the C# and .NET roadmap
Apps belongs to the Workloads stage (beginner level). What you can build.
Other units in this stage
Back to the full C# and .NET roadmap