This is a step-by-step guide to becoming a .NET Engineer, with links to relevant learning resources.
If you want to learn more about .NET technologies, be sure to subscribe to my newsletter.
This roadmap aims to give you an idea about the landscape. The road map will guide you if you need clarification about what to learn next rather than encouraging you to pick what is hype and trendy. It would help if you grew some understanding of why one tool would be better suited for some cases than the other and remember that hype and trendy only sometimes mean best suited for the job.
If you like or are using this project to learn or start your solution, please give it a star. Thanks!
Note that by seniority level, it means:
- Junior: Basic concepts
- Medior: Advanced concepts
- Senior: Expert concepts
Download PDF version.
- Understanding the .NET ecosystem
- Learning resources
- 1. C#
- 2. General Development Skills
- 3. ASP.NET Core
- 4. Client-Side .NET
- 5. Databases
- 6. ORM
- 7. Caching
- 8. Logging
- 9. Real-time communication
- 10. Background tasks
- 11. Object Mapping
- 12. Testing
- 13. Monitoring & Telemetry
- 14. Messaging
- 15. Containerization
- 16. Cloud
- 17. Continuous Integration & Delivery (CI/CD)
- 18. NET Libraries
- Additional considerations
- Additional learning resources
- Tools
Before going into specifics, you need to have a solid understanding of the .NET Ecosystem. Here are a few that you should understand:
In this section, we will look at the main .NET runtimes. We consider .NET runtime as anything that implements ECMA-335 Standard for .NET.
.NET Framework is a software development framework for building and running applications on Windows. .NET Framework consists of Common Language Runtime (CLR), .NET Framework Class Library, and Application workloads (WPF, Windows Forms, and ASP.NET). CLR is part of a shared infrastructure that runs code, jit, does garbage collection (C#, VB.NET, F#), etc. The code that CLR manages is called managed code. Code is compiled into Common Intermediate Language (CIL) and stored in assemblies (with .exe or .dll extension). When an application runs, CLR takes an assembly and uses a just-in-time compiler (JIT) to transpile machine code into code that can run on specific computer architecture.
You can use it for both desktop and web development, but it is limited to Windows development, and it comes preinstalled on Windows.
.NET Core is one of the runtimes in the .NET Ecosystem. It was released in 2016. and it's open-sourced. It does not represent a new version of the .NET Framework and will not replace it. It is an entirely independent version, built to allow cross-platform capability for application development. .NET Core consists of an App Host (dotnet.exe) that runs CLR and Library. It has a Common language runtime (CoreCLR) and .NET Core Class Library. It supports different application workloads, such as ASP.NET Core (MVC and API), console applications, and UWP (currently).
.NET Core can run on different platforms: Windows Client, Server, IoT, Linux, Ubuntu, FreeBSD, Tizen, and Mac OSX, and can be installed side-by-side of different versions per machine or user.
.NET 5 was released in November 2020 with the goal of unifying development for desktop, Web, cloud, mobile, gaming, IoT, and AI applications. The earlier setup goal was to produce a single .NET runtime and framework, cross-platform, integrating the best features of .NET Core, .NET Framework, Xamarin, and Mono. However, due to the global health pandemic, the unification was postponed to .NET 6. .NET 5 is a shared code base for .NET Core, Mono, Xamarin, and future .NET implementations. Also, target framework names (TFMs), which express which version of .NET targeting, are updated, so we now have net5.0. This is for code that runs everywhere. It combines and replaces the netcoreapp and netstandard names and net5.0-windows that represent OS-specific flavors of .NET 5 that include net5.0 plus OS-specific bindings.
.NET 8 is the latest runtime in the .NET Ecosystem. It is released in November 2023. and it unifies development for desktop, Web, cloud, mobile, gaming, IoT, and AI applications. .NET 8 consists of an App Host (dotnet.exe) that runs CLR and Library. It has a Common language runtime (CoreCLR) and .NET 8 Class Library. It also includes ASP.NET Core 8. .NET 8 has nearly identical platform support as .NET Core 3.1 for Windows, macOS, and Linux.
.NET 8 is a Long Term Support (LTS). Those releases are supported for three years after the initial release.
.NET 7 was a Standard Term Support release, supported for six months after a subsequent STS or LTS release.
Different runtimes use different class libraries, e.g., .NET Framework uses .NET Framework class library, while .NET Core contains its class library, as well as Xamarin with its class library. In this way, it's hard to share code between different runtimes, as they use different APIs. Microsoft's solution is the .NET Standard library, released in 2016. It represents a set of (formal) specifications that say which APIs you can use and all runtimes implement it. It is the evolution of Portable Class Libraries (PCL). Specific runtimes implement specific versions of .NET Standard (implementing specific APIs). E.g., .NET Framework 4.8.1 implements .NET Standard 2.0, and .NET 7 implements .NET Standard 2.1 (link).
To learn more about the .NET Ecosystem, check this blog post.
.NET Release Schedule by Microsoft:
C# is a programming language developed by Microsoft. It's a go-to choice for building anything from desktop applications and games (using Unity) to cloud-based solutions and web services. With strong support for object-oriented programming and a rich library, it's designed to be easy and efficient.
The latest version is C# 12, released in November 2023.
You need to understand different C# language features, such as:
- Object-oriented programming (classes, objects, interfaces, inheritance, polymorphism)
- Variables, data types, and operators
- Reference and value types
- Control flow (conditionals, loops)
- Generics
- Exception handling
- Delegates and events
- Assemblies
- Collections
- LINQ (Language Integrated Query)
- Async and await for asynchronous programming
But also .NET libraries and APIs for:
- File I/O and serialization
- Collections and data structures
- Networking
- Multithreading and task parallelism
- Security and cryptography
Resources:
- Microsoft Learn C#.
- Microsoft C# Fundamentals for Absolute Beginners.
- Microsoft C# 101
- Udemy C# for Beginners - Coding From Scratch (.NET Core)
- C# Basics for Beginners: Learn C# Fundamentals by Coding
- Learn dotnet CLI
- Learn.NET official Microsoft tutorials
- Dot Net Perls - Many code examples in C#
- Become a Full-stack .NET Developer - Advanced Topics
- C# language specification - ECMA-334
- Advanced concepts:
- Async/Await by Stephen Toub
- Threading in C# by Joseph Albahari
- Concurrency and Locking
Mastering design patterns, clean code, and version control like Git enables you to write efficient, maintainable code that works and thrives in a team environment. It's the difference between being a coder and a skilled software engineer.
Here, you need to know different principles, such as:
SOLID Principles:
- Single Responsibility Principle (SRP)
- Open/Closed Principle (OCP)
- Liskov Substitution Principle (LSP)
- Interface Segregation Principle (ISP)
- Dependency Inversion Principle (DIP)
But also:
- DRY (Don't Repeat Yourself)
- KISS (Keep It Simple, Stupid)
- YAGNI (You Ain't Gonna Need It)
- Law of Demeter (LoD) or Principle of least knowledge
- Composition over Inheritance
- The principle of least astonishment
- Software architecture styles and patterns (MVC, MVP)
Resources:
- Learn Git
- Learn HTTP(S) protocol
- Learn Data Structures & Algorithms
- Learn Clean Code
- Learn Refactoring fundamentals
- Learn Design Patterns from the book or video tutorials or download cheat sheet.
- Must know patterns are:
- Singleton
- Factory Method
- Adapter
- Facade
- Decorator
- Proxy
- Command
- Template method
- Strategy
- Observer
- Must know patterns are:
- Learn Main software design principles
- Learn SOLID principles of OO Design in depth.
- Learn Fundamentals of Software Architectures
- Learn Microservices and DAPR
- Learn Domain-Driven Design or from the book
It is a cross-platform, high-performance framework developed by Microsoft for building web apps, APIs, and microservices. You can also run your apps on Windows, Linux, or macOS. It's engineered for flexibility and scalability with features like built-in dependency injection and a robust configuration system.
Here, you also need to know web application fundamentals, such as:
- HTML, CSS, and JavaScript for front-end development
- HTTP protocols, request/response model, and RESTful APIs
- Routing, middleware, authentication, and authorization
Resources:
- ASP.NET Core Fundamentals by Scott Alen course
- ASP.NET MVC 5 Fundamentals by Scott Alen course
- Advanced ASP.NET Core 3.1 MVC Udemy course
- Pro ASP.NET Core 6 book
- APIs
- Dependency Injection
- Application Settings & Configurations
- Middlewares
- Filters & Attributes
- Authentication or this Reddit thread
- Authorization
- IdentityServer
- Auth0
- OIDC
If you want to build UIs in .NET, you will need these frameworks. Razor is a template engine for creating dynamic HTML, while Blazor takes it up a notch, letting you build interactive web UIs using C# instead of JavaScript. MAUI is a Xamarin successor made for building cross-platform mobile apps.
Resources:
Good database design ensures efficient data storage and quick retrieval, making your app run smoother and scale easier. SQL, the go-to language for database interaction, gives you the power to query, update, and manage the data you've so carefully designed to store.
Here, you need to know:
- SQL Syntax
- Basics of Database design (normal forms, keys, relationships)
- The Difference Between Inner, Left, Right, and Full Join
- SQL Queries Execution Order
- What is Query Optimizer
Resources:
- Database design
- Learn SQL
- Relational
- NoSQL
- Tools:
- SQLFlow - a great tool to visualize SQL queries.
Object-relational mapping (ORM) is like a translator between your object-oriented C# code and the relational database, eliminating the tedious task of writing SQL queries for basic CRUD operations. Using ORM frameworks like Entity Framework, you can manipulate data as objects in your code, making it more readable and maintainable. This speeds up development, minimizes errors, and lets you focus on complex business logic rather than wrestling with database syntax.
For Entity Framework, you need to know the following:
- DbContext and DbSet for managing database connections and querying data
- Code-First and Database-First approaches for defining data models
- Migrations for managing database schema changes
- Querying data using LINQ and raw SQL
- Tracking changes and saving data
Resources:
Caching is like your app's personal short-term memory, storing frequently accessed data so it can be quickly retrieved without taxing your database. By reducing database load and speeding up data access, caching gives your app the competitive edge it needs to meet user demands for responsiveness and availability.
Resources:
- Memory Cache
- Redis
- Application-Level
Logging captures runtime information, errors, and other crucial data that can help you quickly identify and fix issues, making your application more reliable and secure. Logging frameworks like NLog or Serilog integrate seamlessly into .NET, giving you a real-time diagnostic tool indispensable for monitoring application health, troubleshooting problems, and even gathering insights for future development.
Resources:
Real-time communication technologies, like SignalR in the .NET ecosystem, enable these functionalities by maintaining a constant connection between server and client. They are used in interactive experiences, whether live chat, notifications, or real-time updates.
Resources:
These services run tasks in the background, freeing up your application to focus on user interactions. Whether data processing, automated emails, or periodic clean-ups, background services ensure these tasks don't slow down or interrupt the user experience.
Resources:
Their libraries automate the task of mapping between objects, eliminating the need for repetitive, error-prone manual mapping code. This boosts productivity and minimizes bugs, especially when dealing with complex models and DTOs (Data Transfer Objects).
Resources:
Unit tests focus on isolated pieces of your code, integration tests ensure different parts play well together, and end-to-end tests validate the entire user journey within your application. Together, they form a safety net, catching bugs early, simplifying debugging, and making your codebase robust and maintainable.
Here you need to know:
- Test frameworks (xUnit, NUnit, MSTest)
- Test runners and test explorers
- Asserts and test attributes
- Mocking libraries (Moq, NSubstitute, etc.)
Resources:
- Unit Testing
- Frameworks
- Mocking
- Assertion
- Test Data Generators
- Integration Testing
- Snapshot Testing
- Behavior Testing
- End-to-End Testing
- Performance Testing
These tools provide real-time insights into your application's performance, user behavior, and error rates, enabling you to address issues before they escalate into full-blown problems proactively.
-
Monitoring focuses on the health and availability of services and systems, often triggering alerts for predefined conditions.
-
Telemetry collects, processes, and transmits data from systems, enabling analysis of patterns, trends, and anomalies.
Resources:
Messaging systems act as a middleman between different parts of your system, allowing them to communicate without being directly connected. This decouples your components, making scaling, maintaining, and adding new features easier. Plus, it improves fault tolerance—so if one part fails, it doesn't bring down the whole system.
Resources:
Container solutions encapsulate your .NET application, libraries, and runtime into isolated containers. This enables consistency across multiple development and production environments, resolving dependency issues. With features like layered file systems, you can easily manage container images for ASP.NET, .NET Core, or other .NET services, optimizing build times and resource utilization.
Resources:
Cloud providers provide a layer of APIs to abstract infrastructure and provision it based on security and billing boundaries. The cloud runs on servers in data centers, but the abstractions cleverly give the appearance of interacting with a single "platform" or large application. The ability to quickly provision, configure, and secure resources with cloud providers has been key to the tremendous success and complexity of modern DevOps.
The most popular cloud providers in the market are AWS and Azure, as well as Google Cloud.
Here, you must know how to manage users and administration, networks, virtual servers, etc.
Resources:
CI/CD automates the building, testing, and deployment stages into a streamlined, error-resistant pipeline. This means faster releases, bug fixes, and more time to focus on feature development.
Here you need to know how to:
- Build and deployment tools (MSBuild, dotnet CLI)
- Version control systems (Git, Azure DevOps)
- CI/CD platforms (GitHub Actions, Azure Pipelines, Jenkins, TeamCity)
Resources:
Some useful .NET libraries. Note that not all libraries will be used by everyone, it mainly depends on a project you work on.
- MediatR - Mediator pattern implementation in .NET
- Polly - Fault-handling library that allows expressing policies such as Retry and Circuit Breaker.
- Fluent Validation - .NET validation library for building strongly-typed validation rules.
- Benchmark.NET - .NET library for benchmarking.
- Newstonsoft.json - High-performance JSON framework for .NET.
- Refit - Turns your REST API into a live interface.
- YARP - Reverse proxy server.
- Swashbuckle - Swagger tools for documenting API's built on ASP.NET Core.
In addition to this, you also need to know the following:
Performances play an essential role in .NET applications. Here you need to know:
These tools can help you identify and debug different performance bottlenecks you have in your code. For this, you can use other tools, such as:
Along with tools, you should be aware of different performance best practices for .NET:
-
Caching (in-mem Memory Cache or Redis)
-
Database Optimization (optimize queries, proper indexing, connection pooling)
-
Async Programming (offload all CPU extensive or I/O bound operations to DB, file systems, ext. systems)
-
Use Entity Framework wisely (use eager loading, projections, and optimizations like compiled queries)
-
Memory management (use value types and be cautious with large object graphs. Use dispose pattern to db connections or streams. Avoid boxing/unboxing. Use StringBuilder instead of String for a large number of concatenations.)
-
HTTP Caching (use ETags, Last-Modified headers)
-
Minimize Round-Trips (reduce the number of HTTP requests and database round-trips)
-
Content Delivery Networks (CDNs) (Offload static assets (CSS, JavaScript, images) to CDNs for faster delivery to users)
-
Compression (Enable GZIP or Brotli compression for HTTP responses to reduce data transfer size)
-
Logging and Tracing (Avoid excessive logging in production. Use distributed tracing across microservices.)
-
Parallelism and Concurrency (Utilize parallelism and multithreading for CPU-bound tasks using Parallel class or Task Parallel Library (TPL))
-
Resource Optimization (Optimize images and assets for the Web to reduce load times)
-
HTTP2 over SSL (now make intelligent decisions about the page content)
-
Measure and Monitor Performance (use VS Diagnostic Tools, App Insights, or BenchmarkDotNet)
-
User Span<> instead of collections (spans can represent a contiguous section of memory; this means we can use them to operate over arrays)
Security plays an essential role in application development. The most critical aspects of security in the .NET world are:
-
Authentication and Authorization concepts:
- Cookies
- ASP.NET Core Identity for user management
- .NET OIDC middleware
- OAuth and OpenID Connect for 3rd-party authentication
- JWT (JSON Web Tokens) for token-based authentication
- Role-based and claims-based authorization
-
Cryptography and Data Protection concepts:
- Symmetric and asymmetric encryption algorithms
- .NET Core Data Protection APIs
- Hashing and digital signatures
- Secure random number generation
- Pluralsight learning platform - Learn C#/.NET mostly from Microsoft MVPs.
- Awesome .NET! - A collection of awesome .NET libraries, tools, frameworks, and software.
- Microsoft .NET Architecture Guides
- Learn C# in One Day and Learn It Well - the best for beginners
- C# in Depth: Fourth Edition by Jon Skeet - the best for intermediate
- Concurrency in C# Cookbook: Asynchronous, Parallel, and Multithreaded Programming - the best for advanced
- The C# Yellow (free) - the best book overall
- IAmTimCorey
- Programming with Mosh
- Nick Chapsas
- Milan Jovanovic
- Zoran Horvat
- CodeOpinion, by Derek Comartin
- freeCodeCamp
- Official .NET Blog
- The Morning Dew, aggregator of different info about .NET world, by Alvin Ashcraft.
- You’ve Been Haacked, by Phil Haack.
- Eric Lippert's blog, who worked on C# compiler team.
- Steve Smith, who focus on code qualiy and DDD.
- Andrew Lock, Senior Engineer at Datadog
- Scott Hanselman, Partner Program Manager at Microsoft
- Rick Strahl's Web Log, focus on web and desktop apps in .NET.
- Adam Sitnik, an expert on .NET Performance and Reliability.
- Jimmy Bogard, creator of AutoMapper.
- Vladimir Khorikov, and expert in Testing.
- Ayende @ Rahien, written by Oren Eini, creator of RavenDB.
- Maarten Balliauw, Developer Advocate at JetBrains.
- Khalid Abuhakmeh’s Blog, Developer Advocate at JetBrains.
- Stephen Cleary, the author of "Concurrency in C# Cookbook"
- Scott Brady, an expert on OAuth and web security.
- Jiří Činčura, a project lead for ADO.NET provider for Firebird DB.
- Coding Militia, by João Antunes (Microsoft MVP).
- Michael Shpilt, a software developer working at Microsoft
- Mark Seemann, explains concepts that are not commonly blogged about with C#.
Other .NET Content creators
- Git and some GUI clients - Distibuted source control system.
- Visual Studio - Main code editor for .NET projects.
- Visual Studio Code - Lightweight code editor for different tech stacks, including .NET.
- Rider - Cross-Platform .NET IDE from JetBrains.
- SQL Server Management Studio / Azure Data Studio - IDE for managing any SQL infrastructure, from SQL Server to Azure SQL Database.
- LINQPad - interactively query databases with LINQ.
- ReSharper - rapid refactoring.
- .NET Reflector - .NET decompiler.
- Postman - platform for testing APIs.
- NDepend - static code analyzer.
- NCrunch for Visual Studio - enables developers to run tests in the background as they write code.
If you think the roadmap can be improved, please open a PR with any updates and submit any issues. Also, I will continue to improve this, so you should start this repository, too.
- Open a pull request with improvements
- Discuss ideas in issues
- Spread the word
Dr. Milan Milanović - CTO at 3MD and Microsoft MVP for Developer Technologies.