Set up C# in JetBrains Rider

What is Rider?

JetBrains Rider is an integrated development environment (IDE) for .NET projects. It brings a C# editor, project templates, build controls, debugging, code navigation and analysis into one application. Rider is an editor and development tool, not the C# language or the .NET SDK. For this guide, install a supported .NET SDK so the project can compile and run.

A console application writes output to a terminal-like Run window. It is a good first project because it needs no web server, desktop UI framework or game engine.

Supported operating systems

Rider runs on supported Windows, macOS and Linux systems. JetBrains lists exact operating-system releases, processor architectures and Linux distribution requirements in its current installation guide; check that page before downloading because support changes. Choose the installer for your processor, such as Apple Silicon versus Intel on a Mac. A .NET console project can use the same C# source on these systems when its target framework and libraries support them.

Rider being cross-platform does not make every C# application cross-platform. Windows Forms and WPF target Windows, while other frameworks have their own platform requirements. Follow the linked operating-system guide to install the correct .NET SDK, and verify it with dotnet --info before opening Rider.

Terminal — verify the development SDK

dotnet --info

• Install .NET on Windows
• Install .NET on macOS
• Install .NET on Linux

Choose the right licence

Checked against JetBrains’ published terms on 21 October 2026: Rider has a free licence for individual non-commercial use, including learning, self-education and hobby projects. You activate it through Help > Manage Licenses > Non-commercial use using a JetBrains Account. JetBrains also offers a 30-day trial. A trial is temporary; the non-commercial licence is a separate option.

JetBrains distinguishes developing products for commercial advantage from excluded activities such as content creation. If you plan commercial product development, use an eligible paid individual or organisational subscription. Reassess the licence if a non-commercial project changes purpose, and read the current terms for edge cases. Prices vary by billing period, region and offers, so check Rider’s live pricing page before purchase rather than relying on a fixed amount here.

Eligible students can apply for JetBrains’ free Student Pack. JetBrains currently limits student eligibility to accredited programmes lasting at least one year of full-time study; the Student Pack is for non-commercial educational work, not a job or freelance project. For learning Rider alone, the individual non-commercial licence does not require student verification. Check JetBrains’ current eligibility and licence terms for your situation.

Install Rider

Download Rider through the official JetBrains site. JetBrains recommends its Toolbox App to install and update IDEs; it offers platform-specific installers for Windows, macOS and Linux. A standalone Rider installer is also available if you manage IDE installations yourself. Select the stable release for normal learning, follow the platform installer prompts and start Rider.

Install a supported .NET SDK separately or confirm that your existing SDK is available. A runtime-only installation is insufficient for building a new project. JetBrains documents an optional setting that can download a missing SDK automatically, but checking dotnet --info yourself makes the selected SDK easier to understand and troubleshoot.

1. Check JetBrains’ current Rider system requirements and choose the installer for your OS and processor.
2. Install Rider using Toolbox App or a standalone installer.
3. Install and verify a supported .NET SDK, then launch Rider and choose a licence option.

Confirm the .NET SDK Rider uses

Run dotnet --info in a terminal to confirm that the SDKs list is not empty and to see the selected version and architecture. In Rider, open Settings > Build, Execution, Deployment > Toolset and Build (on macOS, Rider > Settings). Rider normally detects the .NET CLI executable path automatically. If it points to an unexpected installation, set that path to the dotnet executable you verified and review the selected build tool before trying again.

The target framework offered in New Solution depends on the frameworks installed on your system. For this guide, choose .NET 10 only if a compatible .NET 10 SDK is installed; otherwise select a supported target available to your SDK and Rider version. Check the .csproj TargetFramework afterward. If Rider cannot find an SDK, first verify dotnet --info outside the IDE, then reopen Rider or correct its toolset path.

• Understand the SDK and first console project

Create a C# console project

From Rider’s welcome screen choose New Solution, or use File > New Solution. Search for the Console Application template, select C#, give the solution and project a name such as FirstCSharp, choose a writable folder and a supported target framework, then select Create. Rider also lets you add a new project to an existing solution, but one new solution is simpler for a first app.

Open Program.cs in Solution Explorer. That file contains the C# source. The .csproj file records project settings such as the target framework; the solution groups projects. Modern .NET console templates can use top-level statements, so you may see Console.WriteLine directly in Program.cs instead of a visible Main method. Replace the template content with the example below and save.

1. Choose New Solution and a C# Console Application template.
2. Name the project and select an installed, supported target framework.
3. Open Program.cs from Solution Explorer and save the edited code.

Program.cs

Console.WriteLine("Hello, Codectionary!");

• Learn what every part of the program does

Run the app and use the debugger

Rider normally creates a run/debug configuration for an executable console project. Select that configuration in the toolbar and click Run. Rider builds the project and shows Hello, Codectionary! in the Run window. If it says there is no runnable configuration, check that you selected the console project rather than a class library, and inspect the configuration’s Project and Target Framework settings.

To inspect a value, replace Program.cs with the two-line example below. Set a breakpoint beside the Console.WriteLine line in the editor gutter, then click Debug for the selected configuration. Execution pauses before that line. Inspect name in the Debug window or by hovering over it, then use Step Over to execute the line or Resume to continue. The Console tab shows the program’s output. A breakpoint helps inspect running code; compiler errors must be fixed before the program can start.

If the expected output does not appear, save Program.cs, confirm the selected run configuration points to this project, and read the Build or Run window for errors. A missing quote or semicolon is a C# compiler error; it is not a Rider licence or debugger problem.

Program.cs — inspect name before output

string name = "Sam";
Console.WriteLine($"Hello, {name}!");

• Learn about variables and types

Rider, Visual Studio and VS Code

All three can be used for C# development, but their setup and interfaces differ. Pick one that supports your operating system and project; you can still use dotnet CLI commands with any of them. Visual Studio for Mac is retired, so the Visual Studio column here means the current Windows product.

• Visual Studio setup guide
• C# and .NET overview

Syntax

Console.WriteLine("Hello, Codectionary!");

Examples

Console.WriteLine("Hello, Codectionary!");

Best practices

• Check Rider’s current system requirements and install a supported .NET SDK, not just a runtime.
• Verify Rider’s .NET CLI path if it does not find the expected SDK.
• Use a licence that matches the purpose of your project, and check current JetBrains terms before commercial work.
• Use the Build or Run window to diagnose errors before changing debugger settings.

Runtime & versions

.NET runtime. Feature availability depends on the language and runtime version used by your project; consult the official reference below.

Related C# documentation

Specifications & further reading

• JetBrains: Install Rider and supported operating systems
• JetBrains: Create projects and solutions
• JetBrains: Toolset and Build settings
• JetBrains: Run and debug configurations
• JetBrains: Rider pricing and licence conditions
• JetBrains: Register Rider
• JetBrains: Student Pack eligibility
• JetBrains: Educational licence eligibility