Fedora 29 Package Manager - Install .NET Core
Package manager installs are only supported on the x64 architecture. Other architectures, such as ARM, must manually install the .NET Core SDK or manually install the .NET Core Runtime. For more information, see .NET Core dependencies and requirements.
This article describes how to use a package manager to install .NET Core on Fedora 29. 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.
Register Microsoft key and feed
Before installing .NET, you'll need to:
- Register the Microsoft key.
- Register the product repository.
- Install required dependencies.
This only needs to be done once per machine.
Open a terminal and run the following commands.
sudo rpm --import https://packages.microsoft.com/keys/microsoft.asc sudo wget -q -O /etc/yum.repos.d/microsoft-prod.repo https://packages.microsoft.com/config/fedora/29/prod.repo
Install the .NET Core SDK
Update the products available for installation, then install the .NET Core SDK. In your terminal, run the following command.
sudo dnf install dotnet-sdk-3.1
Install the ASP.NET Core runtime
Update the products available for installation, then install the ASP.NET runtime. In your terminal, run the following command.
sudo dnf install aspnetcore-runtime-3.1
Install the .NET Core runtime
Update the products available for installation, then install the .NET Core runtime. In your terminal, run the following command.
sudo dnf install dotnet-runtime-3.1
How to install other versions
The packages added to the package manager feeds are named in a hackable format:
The type of .NET product to install. Valid options are:
Chooses the SDK or the runtime. Valid options are:
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:
- Install the .NET Core 2.2 SDK:
- Install the ASP.NET Core 3.1 runtime:
- Install the .NET Core 2.1 runtime:
If the package 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