DEVELOPER TOOLS · VERIFIED REFERENCE

.NET SDK installation on Linux

Choose an installation method, inspect the result and keep SDK selection reproducible.

An original HamTron Learn guide to a bounded Linux development setup. Read the options before running commands and distinguish installation evidence from application validation.

By the end, you should be able to explain the installer options shown here, inspect an installed SDK and diagnose a command-discovery problem.

Choose an installation method

Use a package-managed installation for a maintained development host when a suitable supported package is available. A scripted installation is useful for isolated builds and automation that need a chosen SDK in a controlled directory. These are different operating choices; the script is not a complete host-management system.

Before installing, record the operating-system release, architecture, intended SDK and destination. Decide who will maintain updates and which account will own the installation.

Read the installer options

This example assumes an approved, integrity-checked copy of dotnet-install.sh is already available in the current directory. Acquiring and verifying that file is a separate prerequisite; this lesson does not distribute an installer.

bash ./dotnet-install.sh --version 10.0.403 --install-dir "$HOME/.local/share/hamtron-dotnet" --no-path
Options used in the worked example
OptionMeaning
--version 10.0.403Request that SDK release.
--install-dirChoose the installation directory.
--no-pathLeave PATH configuration to the operator.

The directory and version are example choices. The command installs an SDK by default. Operating-system dependencies still need attention; downloading files is not evidence that every required native library is present.

Verify what was installed

Inspect the selected executable directly:

"$HOME/.local/share/hamtron-dotnet/dotnet" --info
"$HOME/.local/share/hamtron-dotnet/dotnet" --list-sdks
"$HOME/.local/share/hamtron-dotnet/dotnet" --list-runtimes

In the HamTron development installation observed on 9 November 2026, the output showed Ubuntu 24.04, linux-x64, SDK 10.0.403 and runtime 10.0.14. These are the recorded results for one host, not minimum requirements or a promise for other systems. SDK and runtime numbers need not be identical.

This check establishes installation visibility. It does not show that an application builds, passes its tests or provides effective security monitoring. Record those as separate results.

Make the command discoverable

For a manual installation, configure the current shell explicitly:

export DOTNET_ROOT="$HOME/.local/share/hamtron-dotnet"
export PATH="$DOTNET_ROOT:$DOTNET_ROOT/tools:$PATH"
dotnet --info

The first line identifies the installation root; the second adds executable search locations. These exports apply to this shell and child processes. To retain them across logins, add reviewed entries to the profile used by your shell. Avoid repeatedly appending duplicate entries.

Check native dependencies against the actual Linux distribution and release. For a manually downloaded SDK archive, compare its SHA-512 digest with the publisher's release checksum before extraction. A matching digest checks consistency with that checksum; obtaining the checksum through a trusted channel remains part of the supply process.

Select the project SDK

A project can carry a global.json SDK-selection policy. This example requires an exact SDK and excludes previews:

{
  "sdk": {
    "version": "10.0.403",
    "rollForward": "disable",
    "allowPrerelease": false
  }
}

latestPatch instead permits an installed patch at or above the requested version within the same major, minor and feature band. Choose that policy deliberately; it does not download an SDK. SDK selection is distinct from a project's target runtime.

Run SDK checks from the intended project directory. The command-line SDK resolver searches from the current directory upward for global.json; a missing file in a home directory does not establish that a project lacks one.

Diagnose one failure at a time

Evidence and next checks
ObservationNext check
curl: (2) no URL specifiedInspect the pasted download command. In the recorded HamTron attempt, the download did not start.
Full executable path works; dotnet alone failsInspect the current shell's PATH.
SDK-selection failure inside a projectCompare installed SDKs with that project's selection policy.
Installation succeedsRun the project's restore, build and tests separately; retain their actual output.

In a separate HamTron website staging test, a bundler failed to resolve an asset because public linked outside its filesystem root. An isolated reproduction failed with that layout and built successfully after the assets were copied into the build directory. Check the failing tool and its filesystem inputs before choosing a correction. This result establishes that specific reproduction; it does not validate every asset on another host.

Keep each pasted command on one line when a terminal interface changes line continuations. Review errors before proceeding; do not treat an installation message as an application-validation result.

Continue with the Linux introduction or return to HamTron Learn.

Practice and explained answers

Use the checks and examples on this page to explain each answer before expanding it.

The full executable path works, but dotnet alone is not found. What would you inspect first?

Inspect the current shell’s PATH. This evidence suggests that the executable exists but its directory is not being found by the short command.

Does SDK 10.0.403 alongside runtime 10.0.14 mean this observed installation failed?

No. The recorded installation reported those distinct SDK and runtime versions. Assess the executable output, then run the intended project checks.

Does a global.json selection policy install a missing SDK?

No. It selects among available SDKs according to its policy. Installation is a separate operation.

Editorial credits

Prepared for HamTron Learn. Technical review completed 9 November 2026. Verification covers the stated installer guidance, the recorded Ubuntu installation output and the isolated filesystem-root build reproduction. It does not establish independent academic review, certification or validation of every environment.

Return to Half Echo Learn