Apt Get Install For Mac

Install Git on Mac OS X

There are several ways to install Git on a Mac. In fact, if you've installed XCode (or it's Command Line Tools), Git may already be installed. To find out, open a terminal and enter git --version.

The Helm project provides two ways to fetch and install Helm. These are the official methods to get Helm releases. In addition to that, the Helm community provides methods to install Helm through different package managers. Installation through those methods can be found below the official methods. From the Binary Releases. After installation, type sphinx-build -version on the command prompt. If everything worked fine, you will see the version number for the Sphinx package you just installed. Installation from PyPI also allows you to install the latest development release. You will not generally need (or want) to do this, but it can be useful if you see a possible bug in the latest stable release.

Sudo apt update && sudo apt install -no-install-recommends yarn Note: Due to the use of nodejs instead of node name in some distros, yarn might complain about node not being installed. A workaround for this is to add an alias in your.bashrc file, like so: alias node=nodejs. Mac OS X doesn't have apt-get.There is a package manager called Homebrew that is used instead. This command would be: brew install python. Use Homebrew to install packages that you would otherwise use apt-get for. The page I linked to has an up-to-date way of installing homebrew, but at present, you can install Homebrew as follows.

Sudo apt-get install build-essential Chances are you will need things like gcc to actually do the building so you might as well install those as well. The build-essential package will install.

Apple actually maintain and ship their own fork of Git, but it tends to lag behind mainstream Git by several major versions. You may want to install a newer version of Git using one of the methods below:

Git for Mac Installer

The easiest way to install Git on a Mac is via the stand-alone installer:

  1. Download the latest Git for Mac installer.

  2. Follow the prompts to install Git.

  3. Open a terminal and verify the installation was successful by typing git --version:

  4. Configure your Git username and email using the following commands, replacing Emma's name with your own. These details will be associated with any commits that you create:

  5. (Optional) To make Git remember your username and password when working with HTTPS repositories, configure the git-credential-osxkeychain helper.

Install Git with Homebrew

If you have installed Homebrew to manage packages on OS X, you can follow these instructions to install Git:

  1. Open your terminal and install Git using Homebrew:

  2. Verify the installation was successful by typing which git --version:

  3. Configure your Git username and email using the following commands, replacing Emma's name with your own. These details will be associated with any commits that you create:

  4. (Optional) To make Git remember your username and password when working with HTTPS repositories, install the git-credential-osxkeychain helper.

Install Git with MacPorts

If you have installed MacPorts to manage packages on OS X, you can follow these instructions to install Git:

  1. Open your terminal and update MacPorts:

  2. Search for the latest available Git ports and variants:

  3. Install Git with bash completion, the OS X keychain helper, and the docs:

  4. Configure your Git username and email using the following commands, replacing Emma's name with your own. These details will be associated with any commits that you create:

  5. (Optional) To make Git remember your username and password when working with HTTPS repositories, configure the git-credential-osxkeychain helper.

Install the git-credential-osxkeychain helper

Bitbucket supports pushing and pulling your Git repositories over both SSH and HTTPS. To work with a private repository over HTTPS, you must supply a username and password each time you push or pull. The git-credential-osxkeychain helper allows you to cache your username and password in the OSX keychain, so you don't have to retype it each time.

  1. If you followed the MacPorts or Homebrew instructions above, the helper should already be installed. Otherwise you'll need to download and install it. Open a terminal window and check:

    If you receive a usage statement, skip to step 4. If the helper is not installed, go to step 2.

  2. Use curl to download git-credential-osxkeychain (or download it via your browser) and move it to /usr/local/bin:

  3. Make the file an executable:

  4. Configure git to use the osxkeychain credential helper.

    The next time Git prompts you for a username and password, it will cache them in your keychain for future use.

Install Git with Atlassian Sourcetree

Sourcetree, a free visual Git client for Mac, comes with its own bundled version of Git. You can download Sourcetree here.

To learn how to use Git with Sourcetree (and how to host your Git repositories on Bitbucket) you can follow our comprehensive Git tutorial with Bitbucket and Sourcetree.

Build Git from source on OS X

Building Git can be a little tricky on Mac due to certain libraries moving around between OS X releases. On El Capitan (OS X 10.11), follow these instructions to build Git:

  1. From your terminal install XCode's Command Line Tools (if you haven't already):

  2. Install Homebrew.

  3. Using Homebrew, install openssl:

  4. Clone the Git source (or if you don't yet have a version of Git installed, download and extract it):

  5. To build Git run make with the following flags:

Install Git on Windows

Git for Windows stand-alone installer

  1. Download the latest Git for Windows installer.

  2. When you've successfully started the installer, you should see the Git Setup wizard screen. Follow the Next and Finish prompts to complete the installation. The default options are pretty sensible for most users.

  3. Open a Command Prompt (or Git Bash if during installation you elected not to use Git from the Windows Command Prompt).

  4. Run the following commands to configure your Git username and email using the following commands, replacing Emma's name with your own. These details will be associated with any commits that you create:

  5. Optional: Install the Git credential helper on Windows

    Bitbucket supports pushing and pulling over HTTP to your remote Git repositories on Bitbucket. Every time you interact with the remote repository, you must supply a username/password combination. You can store these credentials, instead of supplying the combination every time, with the Git Credential Manager for Windows.

Install Git with Atlassian Sourcetree

Sourcetree, a free visual Git client for Windows, comes with its own bundled version of Git. You can download Sourcetree here.

To learn how to use Git with Sourcetree (and how to host your Git repositories on Bitbucket) you can follow our comprehensive Git tutorial with Bitbucket and Sourcetree.

Install Git on Linux

Debian / Ubuntu (apt-get)

Git packages are available via apt:

  1. From your shell, install Git using apt-get:

  2. Verify the installation was successful by typing git --version:

  3. Configure your Git username and email using the following commands, replacing Emma's name with your own. These details will be associated with any commits that you create:

Fedora (dnf/yum)

Git packages are available via both yum and dnf:

  1. From your shell, install Git using dnf (or yum, on older versions of Fedora):

    or

  2. Verify the installation was successful by typing git --version:

  3. Configure your Git username and email using the following commands, replacing Emma's name with your own. These details will be associated with any commits that you create

Build Git from source on Linux

Debian / Ubuntu

Git requires the several dependencies to build on Linux. These are available via apt:

  1. From your shell, install the necessary dependencies using apt-get:

  2. Clone the Git source (or if you don't yet have a version of Git installed, download and extract it):

  3. To build Git and install it under /usr, run make:

Fedora

Git requires the several dependencies to build on Linux. These are available via both yum and dnf:

  1. From your shell, install the necessary build dependencies using dnf (or yum, on older versions of Fedora):

    or using yum. For yum, you may need to install the Extra Packages for Enterprise Linux (EPEL) repository first:

  2. Symlink docbook2X to the filename that the Git build expects:

  3. Clone the Git source (or if you don't yet have a version of Git installed, download and extract it):

  4. To build Git and install it under /usr, run make:

Next up:

Setting up a repository

Start next tutorial
-->

.NET Core is supported on Ubuntu. This article describes how to install .NET Core on Ubuntu. When an Ubuntu version falls out of support, .NET Core is no longer supported with that version. However, these instructions may help you to get .NET Core running on those versions, even though it isn't supported.

Install the SDK (which includes the runtime) if you want to develop .NET apps. Or, if you only need to run apps, install the runtime. If you're installing the runtime, we suggest you install the ASP.NET Core runtime as it includes both .NET Core and ASP.NET Core runtimes.

If you've already installed the SDK or runtime, use the dotnet --list-sdks and dotnet --list-runtimes commands to see which versions are installed. For more information, see How to check that .NET Core is already installed.

Package manager installs are only supported on the x64 architecture. Other architectures, such as ARM, must manually install the .NET Core SDK or .NET Core Runtime. For more information, see the manually install section.

Supported distributions

The following table is a list of currently supported .NET Core releases and the versions of Ubuntu they're supported on. These versions remain supported until either the version of .NET Core reaches end-of-support or the version of Ubuntu reaches end-of-life.

  • A ✔️ indicates that the version of Ubuntu or .NET Core is still supported.
  • A ❌ indicates that the version of Ubuntu or .NET Core isn't supported on that Ubuntu release.
  • When both a version of Ubuntu and a version of .NET Core have ✔️, that OS and .NET combination are supported.
Ubuntu.NET Core 2.1.NET Core 3.1.NET 5 Preview (manual install only)
✔️ 20.04 (LTS)✔️ 2.1✔️ 3.1✔️ 5.0 Preview
❌ 19.10✔️ 2.1✔️ 3.1✔️ 5.0 Preview
❌ 19.04✔️ 2.1✔️ 3.1❌ 5.0 Preview
❌ 18.10✔️ 2.1❌ 3.1❌ 5.0 Preview
✔️ 18.04 (LTS)✔️ 2.1✔️ 3.1✔️ 5.0 Preview
❌ 17.10✔️ 2.1❌ 3.1❌ 5.0 Preview
❌ 17.04✔️ 2.1❌ 3.1❌ 5.0 Preview
❌ 16.10❌ 2.1❌ 3.1❌ 5.0 Preview
✔️ 16.04 (LTS)✔️ 2.1✔️ 3.1✔️ 5.0 Preview

The following versions of .NET Core are no longer supported. The downloads for these still remain published:

  • 3.0
  • 2.2
  • 2.0

How to install other versions

The packages added to package manager feeds are named in a hackable format: {product}-{type}-{version}.

  • product
    The type of .NET product to install. Valid options are:

    • dotnet
    • aspnetcore
  • type
    Chooses the SDK or the runtime. Valid options are:

    • sdk
    • runtime
  • version
    The version of the SDK or runtime to install. This article will always give the instructions for the latest supported version. Valid options are any released version, such as:

    • 3.1
    • 3.0
    • 2.1

    It's possible the SDK/runtime you're trying to download is not available for your Linux distribution. For a list of supported distributions, see .NET Core dependencies and requirements.

Examples

  • Install the ASP.NET Core 3.1 runtime: aspnetcore-runtime-3.1
  • Install the .NET Core 2.1 runtime: dotnet-runtime-2.1
  • Install the .NET Core 3.1 SDK: dotnet-sdk-3.1

Package missing

If the package-version combination doesn't work, it's not available. For example, there isn't an ASP.NET Core SDK, the SDK components are included with the .NET Core SDK. The value aspnetcore-sdk-2.2 is incorrect and should be dotnet-sdk-2.2. For a list of Linux distributions supported by .NET Core, see .NET Core dependencies and requirements.

20.04 ✔️

Installing with APT can be done with a few commands. Before you install .NET, run the following commands to add the Microsoft package signing key to your list of trusted keys and add the package repository.

Open a terminal and run the following commands:

Install the SDK

.NET Core SDK allows you to develop apps with .NET Core. If you install .NET Core SDK, you don't need to install the corresponding runtime. To install .NET Core SDK, run the following commands:

Important

If you receive an error message similar to Unable to locate package dotnet-sdk-3.1, see the APT troubleshooting section.

Install the runtime

The .NET Core Runtime allows you to run apps that were made with .NET Core that didn't include the runtime. The following commands install the ASP.NET Core Runtime, which is the most compatible runtime for .NET Core. In your terminal, run the following commands.

Important

If you receive an error message similar to Unable to locate package aspnetcore-runtime-3.1, see the APT troubleshooting section.

As an alternative to the ASP.NET Core Runtime, you can install the .NET Core Runtime that doesn't include ASP.NET Core support: replace aspnetcore-runtime-3.1 in the previous command with dotnet-runtime-3.1.

19.10 ❌

❌ Please note that this version of Ubuntu is no longer supported.

Installing with APT can be done with a few commands. Before you install .NET, run the following commands to add the Microsoft package signing key to your list of trusted keys and add the package repository.

Open a terminal and run the following commands:

Install the SDK

.NET Core SDK allows you to develop apps with .NET Core. If you install .NET Core SDK, you don't need to install the corresponding runtime. To install .NET Core SDK, run the following commands:

Important

If you receive an error message similar to Unable to locate package dotnet-sdk-3.1, see the APT troubleshooting section.

Install the runtime

The .NET Core Runtime allows you to run apps that were made with .NET Core that didn't include the runtime. The following commands install the ASP.NET Core Runtime, which is the most compatible runtime for .NET Core. In your terminal, run the following commands.

Important

If you receive an error message similar to Unable to locate package aspnetcore-runtime-3.1, see the APT troubleshooting section.

As an alternative to the ASP.NET Core Runtime, you can install the .NET Core Runtime that doesn't include ASP.NET Core support: replace aspnetcore-runtime-3.1 in the previous command with dotnet-runtime-3.1.

19.04 ❌

❌ Please note that this version of Ubuntu is no longer supported.

Installing with APT can be done with a few commands. Before you install .NET, run the following commands to add the Microsoft package signing key to your list of trusted keys and add the package repository.

Open a terminal and run the following commands:

Install the SDK

.NET Core SDK allows you to develop apps with .NET Core. If you install .NET Core SDK, you don't need to install the corresponding runtime. To install .NET Core SDK, run the following commands:

Important

If you receive an error message similar to Unable to locate package dotnet-sdk-3.1, see the APT troubleshooting section.

Install the runtime

The .NET Core Runtime allows you to run apps that were made with .NET Core that didn't include the runtime. The following commands install the ASP.NET Core Runtime, which is the most compatible runtime for .NET Core. In your terminal, run the following commands.

Important

If you receive an error message similar to Unable to locate package aspnetcore-runtime-3.1, see the APT troubleshooting section.

As an alternative to the ASP.NET Core Runtime, you can install the .NET Core Runtime that doesn't include ASP.NET Core support: replace aspnetcore-runtime-3.1 in the previous command with dotnet-runtime-3.1.

18.10 ❌

❌ Please note that this version of Ubuntu is no longer supported.

Installing with APT can be done with a few commands. Before you install .NET, run the following commands to add the Microsoft package signing key to your list of trusted keys and add the package repository.

Open a terminal and run the following commands:

Install the SDK

.NET Core SDK allows you to develop apps with .NET Core. If you install .NET Core SDK, you don't need to install the corresponding runtime. To install .NET Core SDK, run the following commands:

Important

If you receive an error message similar to Unable to locate package dotnet-sdk-2.1, see the APT troubleshooting section.

Install the runtime

The .NET Core Runtime allows you to run apps that were made with .NET Core that didn't include the runtime. The following commands install the ASP.NET Core Runtime, which is the most compatible runtime for .NET Core. In your terminal, run the following commands.

Important

Force

If you receive an error message similar to Unable to locate package aspnetcore-runtime-2.1, see the APT troubleshooting section.

As an alternative to the ASP.NET Core Runtime, you can install the .NET Core Runtime that doesn't include ASP.NET Core support: replace aspnetcore-runtime-2.1 in the previous command with dotnet-runtime-2.1.

18.04 ✔️

Installing with APT can be done with a few commands. Before you install .NET, run the following commands to add the Microsoft package signing key to your list of trusted keys and add the package repository.

Open a terminal and run the following commands:

Install the SDK

.NET Core SDK allows you to develop apps with .NET Core. If you install .NET Core SDK, you don't need to install the corresponding runtime. To install .NET Core SDK, run the following commands:

Important

If you receive an error message similar to Unable to locate package dotnet-sdk-3.1, see the APT troubleshooting section.

Install the runtime

The .NET Core Runtime allows you to run apps that were made with .NET Core that didn't include the runtime. The following commands install the ASP.NET Core Runtime, which is the most compatible runtime for .NET Core. In your terminal, run the following commands.

Important

If you receive an error message similar to Unable to locate package aspnetcore-runtime-3.1, see the APT troubleshooting section.

As an alternative to the ASP.NET Core Runtime, you can install the .NET Core Runtime that doesn't include ASP.NET Core support: replace aspnetcore-runtime-3.1 in the previous command with dotnet-runtime-3.1.

17.10 ❌

❌ Please note that this version of Ubuntu is no longer supported.

Installing with APT can be done with a few commands. Before you install .NET, run the following commands to add the Microsoft package signing key to your list of trusted keys and add the package repository.

Open a terminal and run the following commands:

Install the SDK

.NET Core SDK allows you to develop apps with .NET Core. If you install .NET Core SDK, you don't need to install the corresponding runtime. To install .NET Core SDK, run the following commands:

Important

If you receive an error message similar to Unable to locate package dotnet-sdk-2.1, see the APT troubleshooting section.

Install the runtime

The .NET Core Runtime allows you to run apps that were made with .NET Core that didn't include the runtime. The following commands install the ASP.NET Core Runtime, which is the most compatible runtime for .NET Core. In your terminal, run the following commands.

Important

If you receive an error message similar to Unable to locate package aspnetcore-runtime-2.1, see the APT troubleshooting section.

As an alternative to the ASP.NET Core Runtime, you can install the .NET Core Runtime that doesn't include ASP.NET Core support: replace aspnetcore-runtime-2.1 in the previous command with dotnet-runtime-2.1.

17.04 ❌

❌ Please note that this version of Ubuntu is no longer supported.

Installing with APT can be done with a few commands. Before you install .NET, run the following commands to add the Microsoft package signing key to your list of trusted keys and add the package repository.

Open a terminal and run the following commands:

Install the SDK

.NET Core SDK allows you to develop apps with .NET Core. If you install .NET Core SDK, you don't need to install the corresponding runtime. To install .NET Core SDK, run the following commands:

Important

If you receive an error message similar to Unable to locate package dotnet-sdk-2.1, see the APT troubleshooting section.

Install the runtime

The .NET Core Runtime allows you to run apps that were made with .NET Core that didn't include the runtime. The following commands install the ASP.NET Core Runtime, which is the most compatible runtime for .NET Core. In your terminal, run the following commands.

Important

If you receive an error message similar to Unable to locate package aspnetcore-runtime-2.1, see the APT troubleshooting section.

As an alternative to the ASP.NET Core Runtime, you can install the .NET Core Runtime that doesn't include ASP.NET Core support: replace aspnetcore-runtime-2.1 in the previous command with dotnet-runtime-2.1.

16.10 ❌

❌ Please note that this version of Ubuntu is no longer supported.

Installing with APT can be done with a few commands. Before you install .NET, run the following commands to add the Microsoft package signing key to your list of trusted keys and add the package repository.

Open a terminal and run the following commands:

Install the SDK

.NET Core SDK allows you to develop apps with .NET Core. If you install .NET Core SDK, you don't need to install the corresponding runtime. To install .NET Core SDK, run the following commands:

Macbook drivers for mac

Important

If you receive an error message similar to Unable to locate package dotnet-sdk-2.1, see the APT troubleshooting section.

Install the runtime

The .NET Core Runtime allows you to run apps that were made with .NET Core that didn't include the runtime. The following commands install the ASP.NET Core Runtime, which is the most compatible runtime for .NET Core. In your terminal, run the following commands.

Important

If you receive an error message similar to Unable to locate package aspnetcore-runtime-2.1, see the APT troubleshooting section.

As an alternative to the ASP.NET Core Runtime, you can install the .NET Core Runtime that doesn't include ASP.NET Core support: replace aspnetcore-runtime-2.1 in the previous command with dotnet-runtime-2.1.

16.04 ✔️

Installing with APT can be done with a few commands. Before you install .NET, run the following commands to add the Microsoft package signing key to your list of trusted keys and add the package repository.

Open a terminal and run the following commands:

Install the SDK

.NET Core SDK allows you to develop apps with .NET Core. If you install .NET Core SDK, you don't need to install the corresponding runtime. To install .NET Core SDK, run the following commands:

Important

If you receive an error message similar to Unable to locate package dotnet-sdk-3.1, see the APT troubleshooting section.

Install the runtime

The .NET Core Runtime allows you to run apps that were made with .NET Core that didn't include the runtime. The following commands install the ASP.NET Core Runtime, which is the most compatible runtime for .NET Core. In your terminal, run the following commands.

Important

If you receive an error message similar to Unable to locate package aspnetcore-runtime-3.1, see the APT troubleshooting section.

As an alternative to the ASP.NET Core Runtime, you can install the .NET Core Runtime that doesn't include ASP.NET Core support: replace aspnetcore-runtime-3.1 in the previous command with dotnet-runtime-3.1.

APT update SDK or runtime

When a new patch release is available for .NET Core, you can simply upgrade it through APT with the following commands:

APT troubleshooting

This section provides information on common errors you may get while using APT to install .NET Core.

Unable to find package

Package manager installs are only supported on the x64 architecture. Other architectures, such as ARM, must manually install the .NET Core SDK or .NET Core Runtime. For more information, see the manually install section.

Unable to locate Some packages could not be installed

If you receive an error message similar to Unable to locate package {netcore-package} or Some packages could not be installed, run the following commands.

There are two placeholders in the following set of commands.

  • {dotnet-package}
    This represents the .NET Core package you're installing, such as aspnetcore-runtime-3.1. This is used in the sudo apt-get install command below.

  • {os-version}
    This represents the Linux version you are on. This is used in the wget command below.

First, try purging the package list:

Then, try to install .NET Core again. If that doesn't work, you can run a manual install with the following commands:

Failed to fetch

While installing the .NET Core package, you may see an error similar to Failed to fetch .. File has unexpected size .. Mirror sync in progress?. This error could mean that the package feed for .NET Core is being upgraded with newer package versions, and that you should try again later. During an upgrade, the package feed shouldn't be unavailable for more than 30 minutes. If you continually receive this error for more than 30 minutes, please file an issue at https://github.com/dotnet/core/issues.

Snap

A snap is a bundle of an app and its dependencies that works without modification across many different Linux distributions. Snaps are discoverable and installable from the Snap Store. For more information about Snap, see Getting started with Snap.

Only supported versions of .NET Core are available through Snap.

Install the SDK

Snap packages for .NET Core SDK are all published under the same identifier: dotnet-sdk. A specific version of the SDK can be installed by specifying the channel. The SDK includes the coresponding runtime. The following table list the channels:

.NET Core versionSnap package
3.1 (LTS)3.1 or latest/stable
2.1 (LTS)2.1
.NET 5.0 preview5.0/beta

Use the snap install command to install a .NET Core SDK snap package. Use the --channel parameter to indicate which version to install. If this parameter is omitted, latest/stable is used. In this example, 3.1 is specified:

Next, register the dotnet command for the system with the snap alias command:

This command is formatted as: sudo snap alias {package}.{command} {alias}. You can choose any {alias} name you would like. For example, you could name the command after the specific version installed by snap: sudo snap alias dotnet-sdk.dotnet dotnet31. When you use the command dotnet31, you'll invoke this specific version of .NET. But this is incompatible with most tutorials and examples as they expect a dotnet command to be available.

Install the runtime

Snap packages for .NET Core Runtime are each published under their own package identifier. The following table lists the package identifiers:

.NET Core versionSnap package
3.1 (LTS)dotnet-runtime-31
3.0dotnet-runtime-30
2.2dotnet-runtime-22
2.1 (LTS)dotnet-runtime-21

Use the snap install command to install a .NET Core Runtime snap package. In this example, .NET Core 3.1 is installed:

Next, register the dotnet command for the system with the snap alias command:

This command is formatted as: sudo snap alias {package}.{command} {alias}. You can choose any {alias} name you would like. For example, you could name the command after the specific version installed by snap: sudo snap alias dotnet-runtime-31.dotnet dotnet31. When you use the command dotnet31, you'll invoke this specific version of .NET. But this is incompatible with most tutorials and examples as they expect a dotnet command to be available.

SSL Certificate errors

When .NET is installed through Snap, it's possible that on some distros the .NET SSL certificates may not be found and you may receive an error similar to the following during restore:

To resolve this issue, set a few enviornment variables:

The certificate location will vary by distro. Here are the locations for the distros where we have experienced the issue.

  • Fedora - /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem
  • OpenSUSE - /etc/ssl/ca-bundle.pem
  • Solus - /etc/ssl/certs/ca-certificates.crt

Dependencies

When you install with a package manager, these libraries are installed for you. But, if you manually install .NET Core or you publish a self-contained app, you'll need to make sure these libraries are installed:

  • libc6
  • libgcc1
  • libgssapi-krb5-2
  • libicu52 (for 14.x)
  • libicu55 (for 16.x)
  • libicu60 (for 18.x)
  • libicu66 (for 20.x)
  • libssl1.0.0 (for 14.x, 16.x)
  • libssl1.1 (for 18.x, 20.x)
  • libstdc++6
  • zlib1g

For .NET Core apps that use the System.Drawing.Common assembly, you also need the following dependency:

Apt Get Not Found

  • libgdiplus (version 6.0.1 or later)

    Warning

    You can install a recent version of libgdiplus by adding the Mono repository to your system. For more information, see https://www.mono-project.com/download/stable/.

Scripted install

The dotnet-install scripts are used for automation and non-admin installs of the SDK and Runtime. You can download the script from https://dot.net/v1/dotnet-install.sh.

The script defaults to installing the latest SDK long term support (LTS) version, which is .NET Core 3.1. To install the current release, which may not be an (LTS) version, use the -c Current parameter.

To install .NET Core Runtime instead of the SDK, use the --runtime parameter.

You can install a specific version by altering the -c parameter to indicate the specific version. The following command installs .NET Core SDK 3.1.

For more information, see dotnet-install scripts reference.

Manual install

As an alternative to the package managers, you can download and manually install the SDK and runtime. Manual install is usually performed as part of continuous integration testing or on an unsupported Linux distribution. For a developer or user, it's generally better to use a package manager.

If you install .NET Core SDK, you don't need to install the corresponding runtime. First, download a binary release for either the SDK or the runtime from one of the following sites:

  • ✔️ .NET 5.0 preview downloads
  • ✔️ .NET Core 3.1 downloads
  • ✔️ .NET Core 2.1 downloads

Next, extract the downloaded file and use the export command to set variables used by .NET Core and then ensure .NET Core is in PATH.

To extract the runtime and make the .NET Core CLI commands available at the terminal, first download a .NET Core binary release. Then, open a terminal and run the following commands from the directory where the file was saved. The archive file name may be different depending on what you downloaded.

Use the following command to extract the runtime:

Use the following command to extract the SDK:

Tip

The preceding export commands only make the .NET Core CLI commands available for the terminal session in which it was run.

You can edit your shell profile to permanently add the commands. There are a number of different shells available for Linux and each has a different profile. For example:

  • Bash Shell: ~/.bash_profile, ~/.bashrc
  • Korn Shell: ~/.kshrc or .profile
  • Z Shell: ~/.zshrc or .zprofile

Edit the appropriate source file for your shell and add :$HOME/dotnet to the end of the existing PATH statement. If no PATH statement is included, add a new line with export PATH=$PATH:$HOME/dotnet.

Apt-get Install Macof

Also, add export DOTNET_ROOT=$HOME/dotnet to the end of the file.

This approach lets you install different versions into separate locations and choose explicitly which one to use by which application.

Next steps