Microsoft .NET software icon

Microsoft .NET 11.0.0

Microsoft .NET is a free, open-source developer platform that provides the runtime, libraries, compilers and SDK used to build and run C#, F# and Visual Basic applications on Windows, macOS, Linux, Android and iOS.

Updated October 13, 2026
194 MB
4.0

Use the arrow keys to choose a rating, then press Enter or Space to submit it.

Very good 1 user ratings

App Specs

DeveloperMicrosoft
LicenseFreeware
CategoryUtilities
Available platformsWindows, macOS, Linux
Downloads122

Overview

Microsoft .NET is a free, open-source developer platform for building and running applications written mainly in C#. F# and Visual Basic also target it. It combines a runtime that executes programs, a large set of base libraries, language compilers, and the .NET SDK with its command-line tools. Apps built on .NET can run on Windows, macOS, Linux, Android and iOS, on x64, x86 and Arm64 processors. Microsoft maintains the platform together with an open-source community under the .NET Foundation. Its source and binaries carry the MIT license, with other licenses applying on Windows.

The platform covers web sites and services, cloud microservices, desktop and mobile apps, games, Internet of Things devices and machine-learning work. These areas share the same runtime and libraries and differ in the application framework placed on top.

Runtime and SDK packages

.NET has parts that run applications and parts that create them. A user who only needs to run a program installs a runtime. A developer installs the SDK, which already contains the runtimes along with the compilers and the dotnet command-line tool.

On Windows there are three runtime packages, each matched to a kind of application:

  • .NET Runtime is the base layer that runs console programs and other general .NET apps.
  • .NET Desktop Runtime adds what Windows Presentation Foundation (WPF) and Windows Forms programs need, and includes the base runtime.
  • ASP.NET Core Runtime runs web applications and services.

Installing the Desktop Runtime and the ASP.NET Core Runtime together lets a Windows PC run any .NET app. Visual Studio installs and manages its own copy of .NET, separate from copies installed system-wide.

How .NET runs code

Compilers for C# and the other .NET languages do not produce processor-specific machine code directly. They emit Common Intermediate Language (CIL), a CPU-independent instruction set, together with metadata that describes every type and member. Both go into an assembly file, so the same compiled program can run on any processor architecture the runtime supports.

When the program starts, the runtime’s just-in-time (JIT) compiler turns each method into native code on its first call. It compiles only code that actually runs. While the app executes, the runtime supplies services such as a self-tuning garbage collector for automatic memory management. Other services include type and memory safety checks, exception handling, and interop with native libraries and hardware instructions. Developers can still write unsafe code for hand-tuned sections and release resources promptly through the using statement.

The C# language builds on these services with generics, value types, interfaces, reflection, and first-class asynchronous programming through async and await.

Base libraries and NuGet packages

The standard .NET libraries supply ready-made APIs for collections, file and network access, JSON processing through System.Text.Json, cryptography and more. These APIs are tuned for each supported operating system and processor. Functions outside the base libraries come from NuGet, the platform’s package manager. Its public gallery, run by Microsoft, holds over 300,000 packages. A project lists the packages it depends on so the SDK can download and restore them automatically during a build.

Application frameworks

Each kind of app uses an application framework that defines the program’s structure and how its lifecycle runs.

ASP.NET Core for the web

ASP.NET Core is the cross-platform web framework of Microsoft .NET. It serves pages and APIs through Kestrel, its built-in HTTP server, and processes each request through a modular pipeline. Developers choose among Razor Pages and Model-View-Controller for server-rendered sites and minimal APIs for compact web services. They can also choose Blazor for interactive web interfaces written in C# instead of JavaScript. Further options include SignalR for real-time messaging and gRPC for high-speed service-to-service calls. Dependency injection, environment-based configuration, logging, authentication and authorization are part of the framework.

.NET MAUI for mobile and desktop

.NET Multi-platform App UI (.NET MAUI) is the successor to Xamarin.Forms. It builds native apps for Android, iOS, macOS and Windows from one project written in C# and XAML. Its controls map to each platform’s own interface toolkit, such as WinUI 3 on Windows and Mac Catalyst on macOS. Cross-platform APIs reach device features such as sensors, the clipboard, file picking, secure storage and text-to-speech. Building for Apple platforms requires a Mac. Hot reload applies code and XAML edits to a running app without restarting it.

Windows desktop

WPF and Windows Forms remain available for Windows-only desktop programs and run on the Desktop Runtime. .NET also supports cloud services and microservices packaged in containers, 2D and 3D game development, and Internet of Things apps on single-board computers such as the Raspberry Pi.

The dotnet command-line tool

The SDK includes the .NET CLI, a cross-platform toolchain. The dotnet command creates projects from templates, restores packages, builds, runs, tests and publishes applications. It also adds or removes NuGet package and project references, and installs optional SDK workloads such as the mobile tooling. A single dotnet build restores dependencies and compiles the project. The SDK and its tools support work both on a developer’s desktop and in continuous integration (CI).

Publishing options

Developers decide at publishing time how a .NET application reaches other computers:

Mode How it works Trade-off
Framework-dependent The app relies on a .NET runtime already installed on the target system Small output that picks up runtime security patches, but behavior can shift with a newer runtime
Self-contained The runtime is bundled with the app for a chosen platform The developer controls the .NET version, at the cost of larger downloads
Single-file All dependent files are combined into one executable Easy to copy, though startup can be slower
Native AOT The app is compiled ahead of time to native code with no JIT or separate runtime Fast startup and lower memory use, but not every library or feature is supported

ReadyToRun precompilation sits between these approaches, storing native code next to the intermediate code to reduce JIT work at startup. Each platform-specific build targets one operating system and processor pair, such as Windows on x64 or macOS on Arm64. The SDK can also publish a project directly as a container image without a Dockerfile.

.NET and .NET Framework

Microsoft .NET, formerly called .NET Core, is the cross-platform successor to .NET Framework, the original Windows-only implementation. .NET Framework is in maintenance mode and still provides deep access to Windows and Windows Server features for existing software. New features, runtime improvements and new major releases arrive in the modern .NET line, which also receives regular monthly servicing updates.

Key Features

  • Cross-platform managed-code runtime
  • Core libraries and command-line host
  • Side-by-side support for multiple major releases
  • Official packages for Windows, macOS, and Linux

Frequently Asked Questions

What is the difference between the .NET runtime and SDK?

The runtime runs compatible applications. The SDK also includes compilers, templates, and build tools for developers.

Can several .NET versions be installed together?

Yes. Major runtime families can coexist because different applications may target different releases.

Which package should Linux users choose?

The linked x64 archive is portable and requires manual setup. A supported distribution package can be simpler when available from Microsoft.

Similar Apps