Visual Studio 2026, Rider and VS Code: Which IDE Should a .NET + Angular Developer Choose

Version note: The commands in this post were run with .NET 10 SDK (Software Development Kit) 10.0.402. Visual Studio 2026 (18.11) runs only on Windows and JetBrains Rider 2026.2 is not installed on this machine (macOS), so neither IDE (Integrated Development Environment) was run; features, versions and licensing details come from Microsoft Learn, the JetBrains documentation and the official blogs as of November 8, 2026. Visual Studio Code (VS Code) 1.145.2 is installed on this machine.

Guess First

The company building Bookstore is a seven-person team with annual revenue under one million dollars. The backend is a .NET 10 Web API (Application Programming Interface), the frontend is Angular 22. Two people use Visual Studio Community on Windows laptops, three are on MacBooks, one is on Linux, and one says "whatever works". The team lead asks you: "If everyone installs Visual Studio Community and the Mac people get VS Code with C# Dev Kit, it's all free, right?"

Before answering, guess two things. First: on how many of these seven machines can Visual Studio 2026 run at all? Second: in a seven-person commercial team, where does free use of Visual Studio Community and C# Dev Kit end? Both answers are in this post, and both turn the choice from a "favorite editor" debate into a concrete engineering decision.

IDE vs Editor: The Project System and the Language Server

"IDE or editor" is not about icons or themes. An IDE understands the project as well as the code: it reads .csproj and .slnx files, builds with MSBuild, resolves NuGet packages, discovers test projects, launches the debugger and refactors across the whole solution. That is the project system. An editor edits text and gets its language understanding from extensions.

The C# side of the three tools may look like it runs on the same engine, but it does not. Visual Studio 2026 gets C# analysis directly from Roslyn (Microsoft's open-source C# compiler platform) and combines it with its own project system. Rider runs ReSharper's long-developed analysis engine in a backend process and builds its front end on the IntelliJ platform, so its C# inspections come from its own engine rather than from Roslyn analyzers (it also runs Roslyn analyzers separately). VS Code is an editor: C# support comes from the C# extension, which talks to a Roslyn-based language server over LSP (Language Server Protocol), and solution and test management come from C# Dev Kit on top of it.

In practice you feel the difference here: if Go to Definition works in VS Code, the language server understands the code; but when you say "move every class that implements this interface into a new assembly" in a hundred-project solution, the maturity of the project system is what matters. On the Angular side the picture flips: the most mature experience for TypeScript and Angular templates is the Angular Language Service extension in VS Code and the WebStorm features built into Rider; in Visual Studio 2026, Angular projects are added to the solution through a separate JavaScript project system (.esproj).

Platform: Which IDE Runs Where

Here is the answer to the first question. Visual Studio 2026 runs only on Windows, and its system requirements page lists Windows 11 and Windows Server 2019, 2022 and 2025 as supported operating systems; Windows 10 is not on the list. There is no native Visual Studio on the Mac anymore either: Visual Studio for Mac was retired on August 31, 2024, and Microsoft's recommendation for Mac users became VS Code with C# Dev Kit. So on the Bookstore team only the two Windows developers can use Visual Studio 2026; running Windows 11 in a virtual machine such as Parallels on a Mac is a separate licensing and performance question.

Rider and VS Code are cross-platform. JetBrains' installation page lists Windows 10 and 11, macOS 15 and 26, and current releases of Ubuntu, Fedora and Debian for Rider 2026.2; on the hardware side it asks for 4 cores and at least 8 GB of total memory. VS Code's requirements are much lower: the docs say 1 GB of memory and a 1.6 GHz processor are enough, but don't read that without the language server and build host that C# Dev Kit runs in the background. For Visual Studio 2026, Microsoft asks for at least 4 GB of memory, recommends 16 GB for typical professional solutions and, in the page's own words, it works best with 64 GB of memory and 16 cores.

Licensing: Who Can Use What for Free

The answer to the second question is in the license pages. The table below is compiled from the Visual Studio Community page, the C# Dev Kit FAQ (Frequently Asked Questions) and JetBrains' October 2024 announcement; licensing terms change, so reread the official page before you decide.

The Bookstore team has seven people and builds a commercial product. Visual Studio Community's limit for non-enterprise organizations is 5 users; C# Dev Kit's commercial team limit is also 5 developers. So when the team lead says "it's all free", two separate license limits have already been exceeded. The correct calculation is this: either the Windows developers get Visual Studio Professional subscriptions (the subscription also covers C# Dev Kit), or the team moves to commercial Rider licenses. Rider's free license cannot be used for commercial work either; JetBrains also notes that anonymous usage statistics cannot be turned off under that license.

One more note: C# Dev Kit is a closed-source extension; on first launch it asks you to sign in with a Microsoft or organizational account. According to the docs the extension doesn't enforce sign-in, but you may need to sign in with a subscribed account to comply with the EULA (End User License Agreement). The C# extension underneath it (dotnet/vscode-csharp) is open source and can be used on its own. If you have no license budget and the team is larger than 5, working with the C# extension alone is a legal option, but you give up C# Dev Kit features such as Solution Explorer and Test Explorer.

Current Versions and Update Cadence

The three tools update at very different speeds, and that directly affects the enterprise question of "which version do we standardize on". As of November 8, 2026:

• Visual Studio 2026: became GA (General Availability) with 18.0 on November 11, 2025. The latest feature update is 18.11 from October 13, 2026, and the latest servicing release is 18.11.3 from October 29, 2026. The Stable channel gets a feature update every month with servicing releases in between; Microsoft plans an annual release every November alongside the new .NET version, delivered as an in-place update of the previous year's release.
• JetBrains Rider: 2026.2 shipped on July 22, 2026; the 2026.2.2 bug-fix release came on September 16, 2026. Rider ships three major releases a year (2026.1 came at the end of March, 2026.2 in July).
• VS Code: 1.145 shipped on November 4, 2026, and 1.145.2 is installed on this machine. Since 1.111 (March 9, 2026) VS Code ships weekly Stable releases; the monthly rhythm of 2025 has been replaced by a weekly one.

This list is the fastest-aging part of the post. Help > About in Visual Studio, Help > About in Rider and Help > About in VS Code (Code > About Visual Studio Code on macOS) tell you your real version; the tenth post in this series covers the changes between versions separately.

The Angular Side: Two Worlds in One Repo

A .NET + Angular developer's day is split between two languages, and the IDE choice has to cover both. Visual Studio 2026's "Angular and ASP.NET Core" template puts the Angular app into the solution as a separate .esproj project and adds proxy.conf.js plus a helper script for the HTTPS (HTTP Secure) certificate; the Angular version is determined by the Angular CLI (Command Line Interface) on your machine. Rider ships WebStorm's JavaScript and TypeScript support in the box; you don't need to install anything extra for completion, navigation and rename in Angular templates. In VS Code you install the Angular Language Service extension; TypeScript support is already built into the editor.

Deciding by Scenario

There is no single "best IDE"; there are scenarios. The table below summarizes my recommendations based on the platform, licensing and resource facts above:

Common Ground: .editorconfig, the dotnet CLI and global.json

When a team uses three IDEs, the fights are not about themes or shortcuts; they are about the build and the code's formatting changing with the IDE. The fix is to take the rules out of the IDE settings and put them in the repo. All three IDEs read .editorconfig:

root = true

[*]
charset = utf-8
end_of_line = lf
insert_final_newline = true
trim_trailing_whitespace = true

[*.cs]
indent_style = space
indent_size = 4

To see why the settings belong in the repo rather than in the IDE, we wrote a file indented with tabs; that is what a commit looks like from someone whose Rider or VS Code editor is set to tabs. dotnet format reads the same .editorconfig and checks it:

$ dotnet format whitespace --verify-no-changes
./Book.cs(5,1): error WHITESPACE: Fix whitespace formatting. Replace 1 characters with '\s\s\s\s'. [./Bookstore.Core.csproj]
./Book.cs(6,1): error WHITESPACE: Fix whitespace formatting. Replace 1 characters with '\s\s\s\s'. [./Bookstore.Core.csproj]
./Book.cs(7,1): error WHITESPACE: Fix whitespace formatting. Replace 1 characters with '\s\s\s\s'. [./Bookstore.Core.csproj]
$ echo $?
2

Because the exit code is 2, this command breaks the build in a CI (Continuous Integration) pipeline. dotnet format whitespace fixes the file, after which the same check returns 0. Whatever IDE someone uses, the file in the repo and the CLI become the referee. Tying code style rules to severities through .editorconfig is the subject of the fourth post.

The second piece of common ground is the SDK version. IDEs usually use the newest SDK installed on the machine; if someone on the team got a new SDK with a Visual Studio update, build behavior can change silently. global.json pins it:

{
  "sdk": {
    "version": "10.0.100",
    "rollForward": "latestFeature"
  }
}

$ dotnet --version
10.0.402

This machine has 10.0.103 and 10.0.402 installed; the latestFeature policy starts at 10.0.100 and moves up to the highest feature band within the same major and minor, so 10.0.402 was selected. It never moves to 11.0. All three IDEs respect global.json when they open the solution; the C# Dev Kit FAQ names a global.json that asks for an SDK not installed on the machine as the most likely cause of the "A compatible .NET SDK was not found" error.

In Production

Count licenses at the organization level, not per person. Visual Studio Community's 5-user limit and its enterprise definition (250 computers or 1 million dollars in revenue) apply to the whole company, not to a single team. When a company grows, this is usually the line that fails the first audit.

Don't make the IDE part of the build system. Visual Studio doesn't have to be installed on the CI server; .NET projects are built with dotnet build, dotnet test and dotnet format. If a step only works in the IDE (for example a file generated by a designer), treat it as a warning sign.

Manage the update speed. Visual Studio updates monthly, VS Code weekly. In enterprise environments, Visual Studio offers an LTSC option next to the Stable channel (for Professional, Enterprise and Build Tools; the Visual Studio 2026 LTSC is planned for November 2026). For VS Code, keeping extension versions and the recommended extension list in the repo is the subject of the eighth post.

Measure hardware against real workloads. The "minimum" numbers in the docs are the values at which the IDE can start; with the Angular dev server, a database container in Docker and an AI (Artificial Intelligence) assistant running at the same time, even 16 GB of memory can feel tight.

Common Pitfalls

Not building common ground when the team uses different IDEs. If one person's IDE converts line endings to CRLF (carriage return + line feed, the Windows line ending) and another's to LF (line feed), every pull request arrives with a noise diff of hundreds of lines. .editorconfig, .gitattributes and dotnet format --verify-no-changes in CI end that argument.

Committing IDE-specific files. Personal workspace files under .vs/ and .idea/ and user-specific *.user files belong in .gitignore. The exception is deliberately shared settings such as .vscode/extensions.json and Rider's team-shared .DotSettings file.

Reading the word "free" in a single sentence. Visual Studio Community, Rider non-commercial and C# Dev Kit are all free, but each has different conditions. In a seven-person commercial team, all three free limits may already be exceeded.

Trusting the SDK that the IDE installed. Without global.json, the new SDK that came with a Visual Studio update can produce different analyzer warnings and a different build result on one developer's machine; part of every "works on my machine" conversation comes from here.

A Small Experiment

★☆☆ Note the version of each of the three tools on your machine (if installed) from its Help > About screen and compare it with the list in this post. However many versions behind you are, pick the single feature from the release notes that would help you most.

★★☆ Add the .editorconfig above to an existing .NET repo and run dotnet format whitespace --verify-no-changes. How many files violate it? Keep the fix in a separate commit so it doesn't mix with the diff of your real changes.

★★★ Fill in the decision table from this post for your team: how many people on which operating system, whether the company falls under the enterprise definition, and the ratio of Angular to .NET work. Turn the result, with the license cost, into a one-page decision note.

You have picked an IDE; now you need to know what's inside. In the next post we tour Visual Studio 2026: workloads, the .slnx solution format that became the default with .NET 10, Solution Explorer filters and Code Search.