Free tools Windows power users keep installed
One-click scans. No signup required.
ASP.NET Core is Microsoft’s cross-platform framework for building web apps and services. To get started, use the official ASP.NET Core documentation’s first-app tutorial, then choose the app model that fits your project: MVC or Razor Pages for web interfaces, controllers or Minimal APIs for HTTP APIs, and real-time options when the app needs live communication. As of September 30, 2026, .NET 10 is the longest-supported release listed here; the .NET 8-to-9 migration guide is useful if you specifically need to upgrade an existing .NET 8 app.
What is ASP.NET Core?
ASP.NET Core is a framework for building web applications and services. Microsoft describes it as supporting fast, secure, cross-platform, cloud-based apps and services. Its documentation spans tutorials, sample code, fundamentals, API reference, MVC-patterned apps, web APIs, and real-time applications.
That breadth matters when choosing what to learn: ASP.NET Core is not one application pattern. MVC is one option within a platform that also supports page-focused web apps, API endpoints, and real-time experiences. Microsoft Learn is the primary starting point for documentation and examples.
How to start an ASP.NET Core project
- Choose the kind of app first. Decide whether you are building a web interface, an HTTP API, or an app that needs real-time communication. That choice points you toward MVC or Razor Pages, controllers or Minimal APIs, or real-time technologies.
- Follow the first-app tutorial. Use the ASP.NET Core first-app tutorial in Microsoft Learn to create a small working project and get familiar with the development flow before adding application-specific features.
- Use the documentation for the next layer. Move from the tutorial to the relevant fundamentals, sample code, and API reference as the project grows. Prefer examples for the .NET version your project targets.
- Choose a supported .NET release. Check the support horizon before starting or upgrading; the table below reflects Microsoft’s listed lifecycle status as of September 30, 2026.
Should you use MVC, Razor Pages, controllers, Minimal APIs, or real-time features?
Choose based on what the application must deliver, not on the assumption that one model is universally best. MVC and Razor Pages are web-app patterns; controllers and Minimal APIs are approaches for building APIs; real-time options address live interactions. Team familiarity can also affect how quickly a project is built and maintained, while the .NET support schedule affects how often the team needs to plan upgrades.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minute#1 Best Overall
| Option | Best fit | What to learn or compare |
|---|---|---|
| ASP.NET Core MVC | A web application organized around the MVC pattern. | Use the MVC-patterned app guidance and samples. Consider whether the MVC structure suits the way your team wants to organize interface and application behavior. |
| Razor Pages | A web application organized around pages. | Compare its page-oriented approach with MVC for the shape and complexity of your interface. |
| Controller-based APIs | An HTTP API built around controllers. | Use the web API documentation and compare its structure with Minimal APIs, including which approach your team can maintain comfortably. |
| Minimal APIs | An HTTP API built with the Minimal APIs model. | Compare it with controllers against your API’s needs and the organization your project requires. |
| Real-time applications | An application that needs real-time communication rather than only request-and-response interactions. | Start with the real-time application documentation and examples to identify the appropriate approach for the feature. |
Deployment target is another decision input: ASP.NET Core is presented as cross-platform and cloud-oriented, but the specific hosting choice depends on the application and its environment. No single model in the documentation overview is designated as the universal choice for every deployment.
Which .NET version should you use?
The table reports the support status Microsoft listed on September 30, 2026. Support dates can change, so verify the current .NET release and support information when making a decision.
Rank #2
| .NET release | Status on September 30, 2026 | Listed support end | Practical consideration |
|---|---|---|---|
| .NET 10 | LTS | November 2028 | Offers the longest support horizon among the releases listed here. |
| .NET 8 | LTS | November 2026 | Its listed support period is close to ending as of the date above; account for an upgrade in your maintenance plan. |
| .NET 9 | STS | November 2026 | Also approaches its listed support end; consider the short remaining horizon before choosing it for new work. |
Microsoft describes LTS as the stability-oriented option and advises keeping supported releases patched. In practice, weigh the support runway against your team’s upgrade cadence and the compatibility requirements of your application and dependencies. Do not assume that choosing an LTS release removes the need to apply updates or plan future upgrades.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How to migrate an ASP.NET Core 8 app to .NET 9
Microsoft’s .NET 8-to-9 migration guidance calls for installing or selecting the .NET 9 SDK and updating version references where applicable. Treat the migration as a coordinated change to the SDK, project target, and package versions rather than changing just one number.
Rank #3
- Install and select the .NET 9 SDK. Confirm that the development environment uses the .NET 9 SDK for the migration work.
- Review
global.json. If the repository pins an SDK version there, update it as needed so the project selects the intended .NET 9 SDK. - Update the project target. Change the project’s target framework to .NET 9 where applicable.
- Update package versions. Review project and package references and update versions where applicable; check related dependencies for compatibility with the target framework.
- Build and validate the application. Use the migration guide and relevant framework documentation to address build or behavior changes before treating the upgrade as complete.
These are the version-selection and reference updates identified by the migration guidance; the exact files and package changes depend on how the application is structured.
Quick Recap
Best Value
- Applying all key ASP.NET Core components, including MVC for HTML generation, .NET Core, EF Core, ASP.NET Identity, dependency injection, and more
- Integrating ASP.NET Core with leading client-side frameworks, including Bootstrap
- ASP.NET Core code for implementing business logic and data transformations
- Handling configuration, routing, controllers, views, and common tasks (including posting forms and presenting data)
- Performing complementary tasks: error handling, logging, application design, authentication, localization, and more
Where to continue learning
- Tutorials: use the ASP.NET Core first-app tutorial, then follow the tutorial for your selected application model.
- Fundamentals and API reference: consult these when you need to understand platform concepts or verify a framework API.
- Samples: use official sample code to see a feature or application pattern in context.
- Video tutorials: use Microsoft’s ASP.NET Core video tutorials as another learning format alongside the written documentation.
- Migration documentation: follow the version-specific guide when moving an existing app between .NET releases.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
