How to Install .NET

The .NET ecosystem is a powerful and versatile platform for building a wide array of applications, from web services and desktop applications to mobile apps and cloud-native solutions. For developers looking to leverage this robust framework, understanding how to install the correct .NET SDK and runtime is the crucial first step. This guide will walk you through the essential processes for installing .NET on various operating systems, ensuring you have the right tools to begin your development journey.

Understanding .NET Versions and Components

Before diving into the installation process, it’s important to grasp the distinction between the .NET SDK and the .NET Runtime. These two components serve different but complementary purposes.

.NET SDK (Software Development Kit)

The .NET SDK is the comprehensive package for developers. It includes everything you need to build, compile, and debug .NET applications. Key components of the SDK include:

• The .NET CLI (Command-Line Interface): This is the primary tool for interacting with the .NET platform. You’ll use it to create new projects, build your code, run tests, publish applications, and manage NuGet packages.
• The .NET Runtime: The SDK includes the runtime necessary for building applications.
• Compilers: Tools like Roslyn (for C# and F#) are part of the SDK, enabling the translation of your source code into executable code.
• Development Libraries: A rich set of base class libraries (BCL) that provide fundamental functionalities for various development tasks.

You typically install the SDK on your development machine.

.NET Runtime

The .NET Runtime is what allows your .NET applications to execute. It comprises:

• The .NET Core Runtime: This is the environment in which your .NET applications run. It includes the common language runtime (CLR) and the base class libraries (BCL) required for execution.
• The ASP.NET Core Module (for IIS): If you are deploying ASP.NET Core applications to Internet Information Services (IIS), this module is necessary for seamless integration.

There are two primary types of runtimes:

• ASP.NET Core Runtime: For web applications.
• ** .NET Desktop Runtime:** For desktop applications (WPF, Windows Forms, MAUI).

You install the runtime on machines where your applications will be deployed and executed, but not necessarily developed. For development, installing the SDK implicitly installs the necessary runtimes.

Long-Term Support (LTS) vs. Standard Term Support (STS)

Microsoft offers different support lifecycles for .NET versions:

• Long-Term Support (LTS): LTS releases are supported for three years from their initial release. These are recommended for production environments due to their extended stability and support.
• Standard Term Support (STS): STS releases are supported for 18 months from their initial release. These receive newer features more frequently and are suitable for development and testing, or for production environments where regular updates are planned.

Always consider your project’s requirements and deployment strategy when choosing a .NET version and its support lifecycle.

Installing .NET on Windows

Windows is a primary development platform for .NET, offering several straightforward installation methods.

Using the .NET Installer

The most common and recommended method for installing the .NET SDK and runtime on Windows is by using the official installers provided by Microsoft.

1. Navigate to the .NET Download Page: Open your web browser and go to the official .NET download page: https://dotnet.microsoft.com/download.

2. Select the .NET Version: You will see a list of available .NET versions. For most development, it’s advisable to choose the latest LTS version. You can also find older versions if required.

3. Download the Windows Installer: Under the chosen version, locate the “Windows” section. You’ll typically find installers for both the SDK and the Runtime.

   • SDK: Download the “x64” or “x86” installer depending on your system’s architecture. Most modern Windows systems are 64-bit (x64).
   • Runtime: Download the appropriate runtime installer if you only need to run applications and not develop them.

4. Run the Installer: Once the download is complete, double-click the .exe file to launch the installer.

5. Follow the Installation Wizard: The installer is user-friendly.

   • License Agreement: Accept the license terms.
   • Installation Type: Choose “Install .NET SDK” to install the development kit, which includes the runtime. If you only need to run applications, select “Install .NET Runtime.”
   • Installation Location: You can usually accept the default installation path.
   • Completing Installation: Click “Install” and wait for the process to finish.

6. Verify the Installation: After the installation is complete, open a new Command Prompt or PowerShell window. Type the following command and press Enter:

   dotnet --version
   

   This should display the version of the .NET SDK you just installed, confirming a successful installation.

Using Chocolatey (Package Manager)

For users who prefer using package managers, Chocolatey is a popular choice for Windows.

1. Install Chocolatey: If you don’t have Chocolatey installed, follow the instructions on their official website: https://chocolatey.org/install.

2. Open an Administrator Command Prompt or PowerShell: Launch your command-line interface with administrative privileges.

3. Install .NET SDK: To install the latest LTS SDK, run:

   choco install dotnet-sdk -y
   

   To install a specific version (e.g., .NET 6 SDK):

   choco install dotnet-sdk --version 6.0.400 -y
   

4. Verify the Installation: Open a new Command Prompt or PowerShell window and run:

   dotnet --version
   

Using Winget (Windows Package Manager)

Winget is Microsoft’s own package manager for Windows.

1. Ensure Winget is Installed: Winget is usually pre-installed on modern Windows 10 and Windows 11 versions. If not, you can get it from the Microsoft Store.

2. Open a Command Prompt or PowerShell:

3. Install .NET SDK: To install the latest LTS SDK:

   winget install --id Microsoft.DotNet.SDK.6 -e --source winget
   

   Replace 6 with the desired LTS version number (e.g., 7 for .NET 7, 8 for .NET 8).

4. Verify the Installation: Open a new Command Prompt or PowerShell window and run:

   dotnet --version
   

Installing .NET on macOS

macOS users can also easily install .NET using official installers or package managers.

Using the .NET Installer

Similar to Windows, the easiest way to install .NET on macOS is via the official installer.

1. Navigate to the .NET Download Page: Go to https://dotnet.microsoft.com/download.

2. Select the .NET Version: Choose the desired .NET version, preferably the latest LTS.

3. Download the macOS Installer: Under the “macOS” section, download the .pkg installer for the .NET SDK.

4. Run the Installer: Double-click the downloaded .pkg file.

5. Follow the Installation Wizard:

   • Introduction, Read Me, License: Proceed through these initial screens.
   • Installation Type: Select the destination for installation (usually the default).
   • Installation: Click “Install” and enter your administrator password when prompted.

6. Verify the Installation: Open the Terminal application. Type the following command and press Enter:

   dotnet --version
   

   This will display the installed .NET SDK version.

Using Homebrew (Package Manager)

Homebrew is the de facto package manager for macOS, and it simplifies .NET installation significantly.

1. Install Homebrew: If you don’t have Homebrew installed, open Terminal and run the command from the Homebrew website: https://brew.sh/.

2. Update Homebrew: It’s good practice to update Homebrew’s package list before installing anything new:

   brew update
   

3. Install .NET SDK: To install the latest LTS SDK (e.g., .NET 8):

   brew install --cask dotnet-sdk
   

   Homebrew typically installs the latest stable version by default. To install a specific version, you might need to search for its formula or tap a specific repository. For example, to install .NET 6:

   brew install --cask dotnet-sdk@6
   

4. Verify the Installation: Open a new Terminal window and run:

   dotnet --version
   

Installing .NET on Linux

Linux distributions have a variety of installation methods, including package managers and direct downloads.

Using the .NET Script Installer (Recommended for most Linux distributions)

Microsoft provides a convenient script that can install .NET on most Linux distributions.

1. Download the Installation Script:

   • For the latest SDK:
     bash
wget https://dot.net/v1/dotnet-install.sh -O dotnet-install.sh

   • To install a specific version (e.g., .NET 8 SDK):
     bash
wget https://dot.net/v1/dotnet-install.sh -O dotnet-install.sh
chmod +x ./dotnet-install.sh
./dotnet-install.sh --channel 8.0 --runtime dotnet


2. Make the Script Executable:
   bash
chmod +x ./dotnet-install.sh


3. Run the Installation Script:

   • To install the latest SDK and runtime:
     bash
./dotnet-install.sh

   • To install a specific version (e.g., .NET 6 LTS SDK):
     bash
./dotnet-install.sh --channel 6.0

   • To install only the runtime:
     bash
./dotnet-install.sh --runtime aspnetcore --channel 6.0


   The script will typically install .NET in your user’s home directory (~/.dotnet). You might need to add ~/.dotnet to your system’s PATH environment variable to use the dotnet command from any directory. The script often prompts you about this or sets it up automatically.

4. Verify the Installation: Open a new Terminal window and run:

   dotnet --version
   

Using Package Managers (Distribution-Specific)

Many Linux distributions offer .NET packages through their native package managers. This is often the preferred method for ease of updates and system integration.

Ubuntu/Debian-based distributions

1. Import Microsoft Package Repository:
   bash
wget https://packages.microsoft.com/config/ubuntu/$(lsb_release -rs)/packages-microsoft-prod.deb -O packages-microsoft-prod.deb
sudo dpkg -i packages-microsoft-prod.deb
rm packages-microsoft-prod.deb

2. Update Package List:
   bash
sudo apt-get update

3. Install .NET SDK: To install the latest LTS SDK (e.g., .NET 8):
   bash
sudo apt-get install -y dotnet-sdk-8.0

   To install the runtime:
   bash
sudo apt-get install -y aspnetcore-runtime-8.0

4. Verify Installation:
   bash
dotnet --version


Fedora/CentOS/RHEL-based distributions

1. Install .NET SDK: For .NET 8 SDK:
   bash
sudo dnf install -y dotnet-sdk-8.0

   For .NET 6 SDK:
   bash
sudo dnf install -y dotnet-sdk-6.0

2. Verify Installation:
   bash
dotnet --version


Post-Installation Configuration and Best Practices

Once .NET is installed, a few configurations can enhance your development experience.

Setting the PATH Environment Variable

For the dotnet command to be accessible from any directory in your terminal, the .dotnet directory must be included in your system’s PATH environment variable.

• Windows: The installer usually handles this automatically. If not, you can manually add C:Program Filesdotnet (or wherever it was installed) to your system’s PATH environment variables.
• macOS/Linux: If you used the script installer and it didn’t automatically update your shell profile, you’ll need to manually add ~/.dotnet to your PATH. For bash shells, add this line to your ~/.bashrc or ~/.bash_profile file:
  bash
export PATH="$PATH:$HOME/.dotnet"

  For zsh shells, add it to ~/.zshrc:
  bash
export PATH="$PATH:$HOME/.dotnet"

  After modifying the file, either restart your terminal or run source ~/.bashrc (or source ~/.zshrc) for the changes to take effect.

Managing Multiple .NET Versions

It’s common to work with multiple .NET versions simultaneously. The .NET CLI is designed to handle this gracefully.

• Global Tools: You can install global tools, which are .NET applications published as NuGet packages and made available on your command line.
  bash
dotnet tool install --global <package-name>

• Project-Specific SDKs: When you create a new project, you specify the target framework. The dotnet command will automatically select the appropriate installed SDK for that framework. For example, creating a .NET 6 project:
  bash
dotnet new webapp -f net6.0

  If you have both .NET 6 and .NET 8 SDKs installed, the dotnet build command within this project directory will use the .NET 6 SDK.

Visual Studio Code Integration

Visual Studio Code (VS Code) is a popular, lightweight, and extensible code editor. To get the best .NET development experience in VS Code:

1. Install the C# Extension: From the VS Code Extensions view (Ctrl+Shift+X or Cmd+Shift+X), search for “C# Dev Kit” (by Microsoft) and install it. This extension provides IntelliSense, debugging, code navigation, and other essential features for C# and .NET development.
2. Ensure .NET SDK is Installed: VS Code relies on the installed .NET SDK to provide its features.

Visual Studio Integration

Visual Studio (full IDE) offers excellent out-of-the-box support for .NET development. When you install Visual Studio with the “.NET desktop development,” “.NET Core cross-platform development,” or “ASP.NET and web development” workloads, the necessary .NET SDKs and runtimes are typically installed or managed by the Visual Studio installer.

By following these installation steps and best practices, you’ll be well-equipped to start building powerful applications with the .NET platform across Windows, macOS, and Linux.