Public repository of armhf and arm64 APT packages for .NET runtimes and SDKs to install on Raspberry Pis running Raspberry Pi OS (Raspbian).
Vendors like Microsoft, Fedora, and Ubuntu provide official DEB packages for .NET, but none of them support armhf, so they can't be installed on Raspberry Pi OS with the default 32-bit architecture. Microsoft recommends installing .NET on Raspberry Pis using their build-machine–oriented installation script, which neither installs system-wide without extra manual steps, nor automatically updates or cleans up previous versions, nor lets you install the latest minor version without you manually looking up whether STS or LTS is currently newer.
This repository comprises unofficial packages that install official .NET Linux ARM releases built by Microsoft, created from the exact same Linux ARM binary archives that are linked to by the official .NET download pages, release notes, and installation script.
You only have to do this step once per Raspberry Pi.
sudo wget -q https://raspbian.aldaviva.com/aldaviva.gpg.key -O /etc/apt/trusted.gpg.d/aldaviva.gpg
echo "deb https://raspbian.aldaviva.com/ $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/aldaviva.list > /dev/null
sudo apt updateThe OpenPGP key fingerprint is B3BF 3504 BBD0 A81D D82A 8DFB 45D6 6F05 4AB9 A66A.
First, to install a package, choose the package name you want. The name is the concatenation of a name prefix and a versioning suffix. For example, if you want the latest version of the .NET Runtime, the package name would be dotnet-runtime-latest. See the following sections for explanations all the package name possibilities.
| Package name format | |
|---|---|
dotnet-runtime-latest |
|
package type |
version spec |
|
|
There are three package type prefixes to choose from:
dotnet-runtime-for running command-line applicationsaspnetcore-runtime-for running web applicationsdotnet-sdk-for building applications
There are also three version specification suffixes to choose from, to control which versions the package should install and allow upgrades to.
latestinstalls the LTS or STS release with the greatest version numberlatest-ltsinstalls the LTS release with the greatest version number- Specific minor versions install and stick with one release permanently, like
8.0
Note
Long-Term Support (LTS) versions like 8.0 are released every other November with even major version numbers, and come with 3 years of support. Standard Term Support (STS) versions like 7.0 are released in the alternate Novembers with odd version numbers and 1.5 years of support.
Then, once you know which package you want, you can install it with apt install <packagename>, for example, sudo apt install dotnet-runtime-latest.
This will install the latest .NET version, regardless of whether it is an LTS or STS release. It will upgrade to greater major and minor versions, including new STS versions. It will never install previews or release candidates.
For example, if you apt install dotnet-runtime-latest in March 2024, it will install .NET Runtime 8. Later, if you run apt upgrade in December 2024, .NET 9 will have been released, so it will install .NET Runtime 9.
| Installation | Package name | Purpose | Includes |
|---|---|---|---|
| .NET Runtime | dotnet-runtime-latest |
Run .NET CLI apps | |
| ASP.NET Core Runtime | aspnetcore-runtime-latest |
Run .NET web apps | .NET Runtime |
| .NET SDK | dotnet-sdk-latest |
Build .NET apps | .NET & ASP.NET Core Runtimes |
Tip
If you find that a .NET application does not run after a major version upgrade, you can choose a different Roll Forward behavior. For example, you can set the DOTNET_ROLL_FORWARD environment variable to LatestMajor.
This will install the latest Long Term Support .NET version. It can upgrade to greater major and minor LTS versions. It will never install an STS, release candidate, or preview release.
For example, if you apt install dotnet-runtime-latest-lts in March 2024, it will install .NET Runtime 8. Later, if you run apt upgrade in December 2024, it will upgrade to the latest 8.0.* release, but will not install the newly released .NET 9, because 9 is an STS release. It will stay on .NET 8 until November 2025, when .NET 10 is released, which is an LTS version like 8.
| Installation | Package name | Purpose | Includes |
|---|---|---|---|
| .NET Runtime | dotnet-runtime-latest-lts |
Run .NET CLI apps | |
| ASP.NET Core Runtime | aspnetcore-runtime-latest-lts |
Run .NET web apps | .NET Runtime |
| .NET SDK | dotnet-sdk-latest-lts |
Build .NET apps | .NET & ASP.NET Core Runtimes |
Tip
If you find that a .NET application does not run after a major version upgrade, you can choose a different Roll Forward behavior. For example, you can set the DOTNET_ROLL_FORWARD environment variable to LatestMajor.
If you want to stay on a specific minor version of .NET, such as 8.0, then you can apt install dotnet-runtime-8.0 or one of the other numbered packages. This example will install .NET Runtime 8.0 and only ever upgrade it to newer patch versions, like 8.0.3, but never to newer major or minor versions like 9.0 or 10.0. It will not install previews or release candidates either.
| Installation | Package names | Purpose | Includes |
|---|---|---|---|
| .NET Runtime | dotnet-runtime-8.0dotnet-runtime-7.0dotnet-runtime-6.0 |
Run .NET CLI apps | |
| ASP.NET Core Runtime | aspnetcore-runtime-8.0aspnetcore-runtime-7.0aspnetcore-runtime-6.0 |
Run .NET web apps | .NET Runtime |
| .NET SDK | dotnet-sdk-8.0dotnet-sdk-7.0dotnet-sdk-6.0 |
Build .NET apps | .NET & ASP.NET Core Runtimes |
Note
The SDK package versions are numbered like the runtime versions they are released in lockstep with, not with the *.*.100-based SDK numbering. For example, as of 2024-03-25, the latest .NET 8 SDK package is versioned 8.0.3-0, not the 8.0.203 version number reported by the SDK once installed.
| Raspberry Pi OS | .NET 8 | .NET 7 | .NET 6 |
|---|---|---|---|
| Bookworm (12) | ✅ | ✅ | ✅ |
| Bullseye (11) | ✅ | ✅ | ✅ |
| Buster (10) | ✅ | ✅ | ✅ |
Raspberry Pi OS releases
Debian releases
.NET releases
In addition to Raspberry Pi OS, you should also be able to install these DEB packages on ARM builds of Debian and other Debian-based distributions like Ubuntu and Mobian, because these packages are not specific to Raspberry Pi OS and only depend on packages in the standard Debian repository.
- ✅ ARM64 (AArch64/ARMv8, 64-bit)
- ✅ ARM32 (armhf/AArch32/ARMv7, 32-bit)
- ✅ Raspberry Pi 5 or greater
- ✅ Raspberry Pi 4
- ✅ Raspberry Pi 3
- ✅ Raspberry Pi 2
- ✅ Other Raspberry Pis that have an ARMv7 or greater CPU, such as Compute Module 3 and 4, Pi Zero 2 W, and Pi 400
- ⛔ Raspberry Pi 1, Pi Pico, Compute Module 1, and Pi Zero are not supported by .NET because they only have an ARMv6 CPU, and .NET requires ARMv7 or later
show outputdotnet --info
.NET SDK:
Version: 8.0.203
Commit: 5e1ceea679
Workload version: 8.0.200-manifests.4e94be9c
Runtime Environment:
OS Name: raspbian
OS Version: 12
OS Platform: Linux
RID: linux-arm
Base Path: /usr/share/dotnet/sdk/8.0.203/
.NET workloads installed:
There are no installed workloads to display.
Host:
Version: 8.0.3
Architecture: arm
Commit: 9f4b1f5d66
.NET SDKs installed:
8.0.203 [/usr/share/dotnet/sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 8.0.3 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 8.0.3 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Other architectures found:
None
Environment variables:
Not set
global.json file:
Not found
Learn more:
https://aka.ms/dotnet/info
Download .NET:
https://aka.ms/dotnet/download
If you maintain an APT package for a .NET application, you can declare a dependency on one of the packages in this repository to automatically install the correct .NET runtime when a user installs your package.
It is recommended to declare a dependency on a virtual package with a metapackage alternative. This way, it allows users to use newer .NET versions if they already have one installed. If your application targets a minimum version of .NET Runtime 6, for example, you can add this to your package's control file.
Depends: dotnet-runtime-latest | dotnet-runtime-6.0-or-greater
If the user already has .NET Runtime 6, 7, or 8 installed, your app can launch with their existing runtime without downloading any new runtimes. Otherwise, the app package installation will automatically include .NET Runtime 8, or whatever the latest version is at the time.
There are virtual packages to represent minor version inequalities for other packages too, not just the above example (like aspnetcore-6.0-or-greater and dotnet-sdk-6.0-or-later) and other versions (like dotnet-runtime-7.0-or-greater and dotnet-runtime-8.0-or-greater).
To allow your application to run with newer major runtime versions, be sure to add a Roll Forward behavior to your .csproj project file or *.runtimeconfig.json runtime configuration file.
<PropertyGroup>
<RollForward>LatestMajor</RollForward>
</PropertyGroup>{
"runtimeOptions": {
"rollForward": "LatestMajor"
}
}