What Are .NET Frameworks? .NET Framework vs .NET Core vs Modern .NET . A Beginner's Guide

Introduction

If you're new to C# or .NET development, you may have come across terms such as .NET Framework, .NET, .NET Core, ASP.NET Core, and .NET MAUI and wondered how they are related.

So, what are .NET frameworks?

A .NET framework is a collection of libraries, APIs, tools, and components that helps developers build applications without implementing common functionality from scratch. The .NET ecosystem includes frameworks and technologies for building web applications, Web APIs, desktop applications, mobile applications, background services, and data-driven applications.

However, the terminology can be confusing. .NET Framework 4.8, .NET 8, ASP.NET Core, and Entity Framework Core are not the same thing.

In this beginner-friendly guide, you'll learn:

• What .NET is
• What the .NET Framework is
• What .NET Core was
• How modern .NET differs from .NET Framework
• What ASP.NET Core is
• What Entity Framework Core is
• What .NET MAUI is
• What a target framework such as net8.0 means
• The difference between a .NET platform and an application framework

By the end of this article, you'll have a clearer understanding of the .NET ecosystem and the different frameworks used to build .NET applications. 

---

What Is a Framework?

Before looking at .NET specifically, let's understand what a framework is.

Suppose you want to build a web application.

Without a framework, you would have to implement many common features yourself:

• HTTP handling

• Routing

• Configuration

• Dependency management

• Authentication

• Logging

• Serialization

• Database communication

A framework provides reusable components for these common tasks.

Instead of building everything from scratch, you can use the framework's APIs and libraries.

Think of it like this:

Your Application
       |
       v
    Framework
       |
       v
 Runtime + Libraries + Operating System

The framework provides building blocks that your application can use.

---

What Is .NET?

.NET is Microsoft's development platform for building applications.

It provides:

• Runtime

• Libraries

• SDK

• Compilers

• CLI tools

• Development frameworks

• Application models

You can use .NET with languages such as:

• C#

• F#

• Visual Basic

C# is the most commonly associated language with modern .NET development.

---

What Is .NET Framework?

.NET Framework is the original Windows-focused .NET implementation.

It was introduced by Microsoft in the early 2000s and has been used to build many Windows applications and web applications.

For example, applications targeting .NET Framework may use:

.NET Framework 4.8

or:

.NET Framework 4.7.2

Common technologies associated with .NET Framework include:

• Windows Forms

• WPF

• ASP.NET

• ASP.NET MVC

• Windows services

• WCF

.NET Framework is primarily associated with Windows.

---

What Is Modern .NET?

Microsoft's modern .NET platform evolved from .NET Core.

Today, the unified platform is generally referred to simply as .NET.

For example:

.NET 6
.NET 7
.NET 8
.NET 9
.NET 10

Modern .NET is designed to be:

• Cross-platform

• High-performance

• Open source

• Cloud-friendly

• Suitable for containers

• Suitable for modern web applications

You can run modern .NET applications on:

• Windows

• Linux

• macOS

---

What Was .NET Core?

Before the modern unified .NET platform, Microsoft developed .NET Core.

.NET Core was Microsoft's cross-platform implementation of .NET.

Versions included:

.NET Core 1.0
.NET Core 2.0
.NET Core 3.0
.NET Core 3.1

After .NET Core 3.1, Microsoft moved to a unified naming scheme.

The next major version was:

.NET 5

Notice that Microsoft dropped the word Core.

The naming then continued with:

.NET 6
.NET 7
.NET 8
.NET 9
.NET 10

So you can think of the evolution roughly like this:

---

.NET Framework vs Modern .NET

One of the most common questions is:

Is .NET Framework the same as .NET?

No.

They are related technologies, but they are different generations of the platform.

If you are maintaining an existing enterprise application, you may encounter:

.NET Framework 4.7.2
.NET Framework 4.8

If you're starting a new modern application, you will commonly encounter:

net8.0
net9.0
net10.0

---

What Is ASP.NET Core?

Another common source of confusion is ASP.NET Core.

ASP.NET Core is a web framework built on modern .NET.

It is used to build:

• Web APIs

• Web applications

• Minimal APIs

• MVC applications

• Razor Pages

• Real-time applications using SignalR

For example, you can create a Web API using:

dotnet new webapi

The application runs on the modern .NET runtime and uses ASP.NET Core for web development.

Think of it this way:

.NET
 |
 +-- ASP.NET Core
 |      |
 |      +-- Web APIs
 |      +-- MVC
 |      +-- Razor Pages
 |      +-- Minimal APIs
 |
 +-- Console applications
 |
 +-- Worker Services
 |
 +-- Other application types

---

What Is a Target Framework?

You may also see something like this in a .csproj file:

<TargetFramework>net8.0</TargetFramework>

This is called the Target Framework Moniker, or TFM.

It tells .NET which target framework your application is built for.

For example:

<TargetFramework>net8.0</TargetFramework>

means the application targets .NET 8.

Another example:

<TargetFramework>net10.0</TargetFramework>

means the application targets .NET 10.

For a .NET Framework application, you might see:

<TargetFramework>net48</TargetFramework>

which represents .NET Framework 4.8.

---

What Does net8.0 Mean?

Let's break it down.

net8.0

means:

net  → .NET
8.0  → version 8.0

Similarly:

net10.0

means:

.NET 10

These identifiers are used throughout .NET projects and tooling.

For example:

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <TargetFramework>net8.0</TargetFramework>
  </PropertyGroup>

</Project>

The project is targeting .NET 8.

---

What Is a .NET Application Framework?

The .NET ecosystem contains frameworks designed for specific types of applications.

For example:

ASP.NET Core

Used for web development.

Web API
MVC
Razor Pages
Minimal APIs
SignalR

Windows Forms

Used to create Windows desktop applications.

WPF

Used to build Windows desktop applications with XAML-based user interfaces.

.NET MAUI

Used to build applications targeting multiple platforms from a shared codebase.

Entity Framework Core

Used for data access and object-relational mapping.

For example:

var users = await dbContext.Users.ToListAsync();

Entity Framework Core handles much of the database interaction for you.

---

Framework vs Library

Another common question is:

What's the difference between a framework and a library?

A library generally provides reusable functionality that your application calls.

For example:

JsonSerializer.Serialize(customer);

Your application calls the library.

A framework generally provides a larger application structure and controls parts of the application's execution flow.

A simplified way to remember this is:

Library:
Your code → calls the library

Framework:
Framework → provides the application structure and calls your code

This distinction is sometimes described using the concept of Inversion of Control.

The real-world distinction can be more nuanced, but this mental model is useful for beginners.

---

What Framework Should You Use?

It depends on the type of application you're building.

The underlying platform can still be modern .NET.

For example:

.NET 10
   |
   +-- ASP.NET Core
   |
   +-- Entity Framework Core
   |
   +-- Worker Services
   |
   +-- .NET MAUI

---

How Do I Check Which .NET Version My Project Uses?

Open the .csproj file.

Look for:

<TargetFramework>net8.0</TargetFramework>

You can also use the .NET CLI to inspect project information.

For example:

dotnet --info

This shows information about the installed SDKs and runtimes.

Remember that the installed SDK version and the project's target framework don't necessarily have to be the same.

You might have:

Installed SDK:
.NET 10

Project:
net8.0

This is possible because multiple .NET SDK versions can coexist on the same computer.

---

Why Are There So Many .NET Terms?

If you're new to .NET, the terminology can seem confusing.

Here's a simple summary:

Summary

The .NET ecosystem contains several technologies designed for different application development scenarios.

The most important distinction to remember is that .NET Framework and modern .NET are different generations of Microsoft's platform.

Here's a quick summary:

The simplest way to remember the terminology is:

.NET
 |
 +-- Application frameworks
 |      |
 |      +-- ASP.NET Core
 |      +-- .NET MAUI
 |      +-- Entity Framework Core
 |
 +-- Target frameworks
        |
        +-- net8.0
        +-- net9.0
        +-- net10.0

If you're learning modern C# development, understanding these terms will help you navigate ASP.NET Core projects, .csproj files, NuGet packages, .NET SDKs, and different application types more confidently.

For most new cross-platform application development, you'll encounter modern .NET rather than the older .NET Framework. Existing enterprise applications, however, may still target versions such as .NET Framework 4.7.2 or 4.8, so knowing the difference remains important for .NET developers.

---

Frequently Asked Questions

Is .NET Framework the same as .NET?

No. .NET Framework is the older Windows-focused implementation, while modern .NET is the unified, cross-platform platform that followed .NET Core.

Is .NET Core still used?

The name .NET Core was used for earlier versions of Microsoft's cross-platform .NET implementation. Starting with .NET 5, Microsoft adopted the unified .NET name.

Is ASP.NET Core a .NET framework?

ASP.NET Core is Microsoft's web framework for building web applications and services on modern .NET.

What does net8.0 mean?

net8.0 is a Target Framework Moniker that indicates that a project targets .NET 8.

Is .NET Framework 4.8 the same as .NET 8?

No. They are different generations of Microsoft's .NET platform.

.NET Framework 4.8 belongs to the older Windows-focused .NET Framework line, while .NET 8 is part of modern .NET.

Which .NET framework is used for Web API?

Modern .NET Web APIs are typically built using ASP.NET Core.

---

Conclusion

The term “.NET framework” can refer to several related concepts, so understanding the terminology is important.

The key points are:

• .NET Framework is the older, primarily Windows-focused .NET implementation.

• .NET Core was Microsoft's earlier cross-platform .NET implementation.

• Modern .NET is the unified platform that began with .NET 5.

• ASP.NET Core is the web framework used to build modern .NET web applications and APIs.

• Entity Framework Core provides data-access and ORM capabilities.

• .NET MAUI provides cross-platform application development capabilities.

• A Target Framework such as net8.0 specifies what .NET platform/version a project targets.

If you're starting a new application today, understanding the difference between the .NET platform, application frameworks, and target frameworks will make it much easier to choose the right technology and understand your project's .csproj file.