English
Install the tools
What we need and why
Table 2.1 lists the tools of the whole tutorial. Install them all now, even those needed only later: then a missing tool will never interrupt a topic halfway.
Table 2.1. Development tools
| Tool | Version | Used for |
|---|---|---|
| .NET SDK | 10.0.403 or later in the 10.0 line | compiling and running the C# projects, dotnet commands |
| Node.js with npm | 24 | the Angular CLI, building and testing the client |
| Docker Desktop | current | PostgreSQL for development and for the tests |
| PowerShell | 7 | the Run.ps1 developer commands |
| Git | current | version control; GitHub for CI/CD |
| An IDE | Visual Studio 2026, JetBrains Rider or Visual Studio Code | writing and debugging the code |
The commands below are for Windows and use winget, the package manager built into Windows 10 and 11; run them in a terminal (Windows Terminal). On macOS use the installers from the linked sites or Homebrew; on Linux use the distribution's package manager. After installing, open a new terminal, so that it picks up the updated PATH.
Step 1. The .NET SDK
The SDK (software development kit) contains the compiler, the dotnet command-line tool and the runtimes. Install .NET 10:
powershell
winget install Microsoft.DotNet.SDK.10Check
powershell
dotnet --list-sdksThe list contains a line starting with 10.0., and the number after it is 403 or greater, for example 10.0.404 [C:\Program Files\dotnet\sdk]. Other SDKs in the list do not matter: topic 2 pins the version for this repository.
Step 2. PowerShell 7
Windows comes with Windows PowerShell 5.1; we need the cross-platform PowerShell 7 (the command is pwsh, not powershell):
powershell
winget install Microsoft.PowerShellFrom now on, run every command of the tutorial in PowerShell 7. In Windows Terminal, make it the default profile (Settings → Startup → Default profile → PowerShell).
Check
powershell
$PSVersionTable.PSVersionThe major version is 7.
Step 3. Git
powershell
winget install Git.GitTell Git who you are; this name and email are written into every commit:
powershell
git config --global user.name "Your Name"powershell
git config --global user.email "[email protected]"Make main the name of the first branch in new repositories:
powershell
git config --global init.defaultBranch mainCheck
git --version prints a version, and git config --global --list shows your name and email.
Step 4. Docker Desktop
Docker runs applications in containers: isolated processes with their own file system, started from ready-made images. We use it to run PostgreSQL without installing it into the system, and the tests use it to start a fresh database of their own. Install Docker Desktop:
powershell
winget install Docker.DockerDesktopOn Windows, Docker Desktop runs Linux containers in WSL 2 (the Windows Subsystem for Linux); the installer offers to enable it, and Windows may need a restart. Start Docker Desktop and wait until it says that the engine is running.
Check
powershell
docker run --rm hello-worldDocker downloads a tiny image and prints "Hello from Docker!". The --rm option deletes the container after it exits.
Step 5. Node.js 24
Node.js runs JavaScript outside the browser; we need it for the Angular command-line tools (topic 15). The project requires Node.js 24, the version its CI uses. Download the installer of version 24 from nodejs.org (choose "v24" in the version list), or, if you need several Node.js versions on one computer, install a version manager such as fnm and run fnm install 24.
Check
node --version prints v24. and a minor version, npm --version prints a version.
Step 6. An IDE
Any of the following works; the tutorial does not depend on the IDE:
- Visual Studio 2026 (Windows, the free Community edition) with the "ASP.NET and web development" workload;
- JetBrains Rider (Windows, macOS, Linux, free for non-commercial use);
- Visual Studio Code with the C# Dev Kit extension. VS Code is also the most convenient editor for the Angular client (topics 15–21) with the Angular Language Service extension.
Check everything at once
Run the five commands one after another. Each must print a version without an error:
powershell
dotnet --versionpowershell
node --versionpowershell
docker --versionpowershell
git --versionpowershell
pwsh --versionA tool "is not recognized"
The program is installed, but the terminal was opened before the installation and still has the old PATH. Close the terminal and open a new one; if that does not help, sign out of Windows and in again.