Installing the .NET 9 SDK
Install .NET SDK on Windows, macOS and Linux; verify with `dotnet --info`.
About
Subtitle: Set up the .NET 10 development environment and verify your first SDK installation.
Difficulty Beginner
Estimated Reading Time 5--7 minutes
Estimated Practice Time 10--15 minutes
Prerequisites Basic understanding of .NET and command-line tools
Learning Outcomes
By the end of this module, you will be able to:
- Understand what the .NET SDK is.
- Understand the difference between the SDK and runtime.
- Install the .NET 10 SDK.
- Verify the installation.
- Check installed SDKs and runtimes.
- Create and run a basic .NET application.
- Troubleshoot common installation problems.
Introduction
What is the .NET SDK?
The .NET SDK (Software Development Kit) is the collection of tools required to build, run, test, and publish .NET applications.
If you want to develop an ASP.NET Core application, console application, Web API, or other .NET application, you normally install the SDK on your development machine.
Think of it this way:
Runtime = tools required to run an application.
SDK = tools required to build and develop an application.
For development, you generally need the SDK.
Why install .NET 10 SDK?
The .NET 10 SDK provides the development tools for applications targeting the .NET 10 platform, including:
- C# compiler
dotnetCLI- MSBuild
- Project templates
- Build tools
- Testing tools
- Publishing tools
Real-Life Analogy
Imagine you want to build furniture.
The finished furniture is your application.
The .NET Runtime is like the environment where the finished furniture can be used.
The .NET SDK is your complete workshop:
.NET SDK
│
├── Compiler
├── CLI
├── MSBuild
├── Templates
├── Testing tools
└── Publishing tools
│
▼
Build .NET Application
Without the workshop, building the furniture would be difficult.
Similarly, without the SDK, you cannot properly develop .NET applications.
Architecture Diagram
The SDK provides the development tools, while the runtime provides the environment required to execute a .NET application.
Concept Explanation
1. What is an SDK?
SDK stands for Software Development Kit.
An SDK is a collection of tools that developers use to create software for a particular platform.
For .NET development, the SDK includes tools such as:
- Compiler
- CLI
- Build system
- Templates
- Testing support
- Publishing tools
2. What is the .NET CLI?
The .NET CLI is the command-line interface for .NET.
After installing the SDK, you can use commands such as:
dotnet --version
dotnet new console
dotnet build
dotnet run
dotnet test
dotnet publish
The dotnet command is one of the most important tools you will use as
a .NET developer.
3. SDK vs Runtime
Component Purpose
.NET SDK Develop applications .NET Runtime Run applications ASP.NET Core Runtime Run ASP.NET Core applications .NET SDK Includes development tooling and required runtimes
Tip: If you are setting up a machine for development, install the SDK, not only the runtime.
Installing .NET 10 SDK
The installation process depends on your operating system.
The general process is:
Download SDK
↓
Install SDK
↓
Open Terminal
↓
Run dotnet --version
↓
Verify .NET 10
Windows
Step 1 --- Download the .NET 10 SDK
Download the https://dotnet.microsoft.com/en-us/download/dotnet/10.0 from Microsoft's official .NET download page.
Choose the SDK rather than only the runtime.
For most modern Windows development machines, the appropriate architecture is x64.
Step 2 --- Run the installer
Open the downloaded installer.
Follow the installation wizard:
Welcome
↓
Accept License
↓
Install
↓
Installation Complete
The installer configures the required .NET development components.
Step 3 --- Open a new terminal
After installation, open a new Command Prompt, PowerShell, or Windows Terminal window.
This is important because environment changes may not be available in an already-open terminal.
Step 4 --- Verify the SDK
Run:
dotnet --version
You should see a .NET 10 SDK version, for example:
10.0.xxx
The exact patch number can change as Microsoft releases updates.
macOS
Step 1 --- Download the .NET 10 SDK
Download the .NET 10 SDK installer appropriate for your Mac architecture.
Modern Apple Silicon Macs use:
Arm64
Intel Macs use:
x64
Step 2 --- Install the SDK
Open the downloaded installer and complete the installation.
Step 3 --- Verify
Open Terminal:
dotnet --version
A .NET 10 installation should report a version beginning with:
10.0
Linux
The installation process varies by Linux distribution.
For Ubuntu and other supported distributions, Microsoft provides package-based installation instructions.
After installing the SDK, verify it with:
dotnet --version
You should see a version beginning with:
10.0
Note: Avoid copying installation commands intended for a different Linux distribution. Package names and repositories can differ.
Verify the Installation
Installing the SDK is only half the job. Always verify it.
Check the SDK version
dotnet --version
Example:
10.0.100
Check detailed .NET information
Run:
dotnet --info
This provides information such as:
- SDK version
- Runtime versions
- Operating system
- Architecture
- SDK installation location
Example:
.NET SDK:
Version: 10.0.xxx
Workload version: ...
MSBuild version: ...
Runtime Environment:
OS Name: Windows
OS Version: ...
OS Platform: Windows
RID: win-x64
Check All Installed SDKs
Use:
dotnet --list-sdks
Example:
8.0.xxx
9.0.xxx
10.0.xxx
This means multiple SDK versions are installed.
That is completely normal.
A developer may work on different projects requiring different .NET versions.
Check All Installed Runtimes
Use:
dotnet --list-runtimes
This displays the runtimes currently installed on your machine.
Test with a Real Project
The best verification is to create a small application.
Create a console application:
dotnet new console -n HelloDotnet
Move into the project:
cd HelloDotnet
Run it:
dotnet run
You should see output similar to:
Hello, World!
You have now confirmed that the SDK can create, build, and execute a .NET application.
Internal Workflow
When you execute:
dotnet run
the process roughly looks like this:
The important idea is:
The SDK is responsible for the development/build side of the process.
Understanding the dotnet Commands
Command Purpose
dotnet --version Shows active SDK version
dotnet --info Shows detailed environment information
dotnet --list-sdks Lists installed SDKs
dotnet --list-runtimes Lists installed runtimes
dotnet new Creates a project
dotnet build Builds a project
dotnet run Builds and runs a project
dotnet test Runs tests
dotnet publish Creates deployable application output
Common Installation Problems
dotnet is not recognized
If you see an error similar to:
'dotnet' is not recognized...
try:
- Close the terminal.
- Open a new terminal.
- Run:
dotnet --version
If it still fails, verify that the SDK installation completed successfully and that the .NET installation directory is available through the system PATH.
Wrong SDK version appears
You might run:
dotnet --version
and receive:
9.0.xxx
even though you installed .NET 10.
First check:
dotnet --list-sdks
If 10.0 is present, the project or SDK selection rules may be determining which SDK is used.
Check whether the project contains a global.json file.
Example:
{
"sdk": {
"version": "9.0.100"
}
}
This file can control which SDK version is selected for a project.
Tip: Don't uninstall older SDKs just because .NET 10 is installed. Different projects can legitimately require different SDK versions.
Best Practices
Best Practice
- Install the SDK for development.
- Verify installation using
dotnet --version. - Use
dotnet --infowhen troubleshooting. - Keep supported SDK versions updated.
- Keep older SDKs when existing projects depend on them.
- Understand the difference between SDK and runtime.
- Check
global.jsonwhen an unexpected SDK is selected. - Use the appropriate OS architecture.
- Use official Microsoft installation packages.
- Restart your terminal after installation.
- Test the installation by creating a small project.
- Don't manually modify PATH unless necessary.
- Don't delete SDK versions blindly.
- Use
dotnet --list-sdksto inspect installed versions. - Use
dotnet --list-runtimesto inspect runtimes. - Keep development environments consistent across teams.
- Document the required SDK version for production projects.
Quick Installation Checklist
☐ Download .NET 10 SDK
☐ Install the SDK
☐ Open a new terminal
☐ Run dotnet --version
☐ Run dotnet --info
☐ Run dotnet --list-sdks
☐ Create a test project
☐ Run dotnet run
☐ Confirm "Hello, World!"
Key Takeaways
- The .NET SDK is the development toolkit for .NET applications.
- The SDK contains the
dotnetCLI and build tooling. - Installing only the runtime is not sufficient for normal development.
- Use
dotnet --versionto check the active SDK. - Use
dotnet --list-sdksto see all installed SDKs. - Use
dotnet --infowhen troubleshooting. - Multiple SDK versions can coexist on the same machine.
- A simple
dotnet new+dotnet runtest confirms that your development environment is working. global.jsoncan influence which SDK a project uses.
Revision Checklist
Before moving to the next topic, make sure you can answer:
- What is the .NET SDK?
- What is the difference between SDK and runtime?
- Why does a developer need the SDK?
- What does
dotnet --versiondo? - What does
dotnet --infodo? - How do you list installed SDKs?
- How do you list installed runtimes?
- How do you create a console application?
- How do you run a .NET application?
- What is
global.jsonused for? - Can multiple .NET SDK versions be installed together?
Recommended Roadmap Progress
✓ Completed
How the Web Works
▶ Current
Installing the .NET 10 SDK
→ Next
Visual Studio 2026
Further Reading
Continue your roadmap with:
- Visual Studio 2026 --- understand the foundation of web applications.
- Terminsl & Command Line Basics --- learn the primary IDE used for .NET development.
- Git Basics --- understand how a .NET project is organized.
- C# Fundamentals --- strengthen the language fundamentals used by .NET applications.
Last updated 10/9/2026
Your notes
Sign in to save personal notes on this topic — they'll sync across your devices.
Was this tutorial helpful?
Help us create more free learning resources. Learn more
