.NET Tools #
Essential productivity kit for .NET and game developers
[.NET Tools](https://blog.jetbrains.com/dotnet/category/net-tools/)
[Releases](https://blog.jetbrains.com/dotnet/category/releases/)
[Rider](https://blog.jetbrains.com/dotnet/category/rider/)
We’ve released version 2026.2.2 of ReSharper, Rider, and .NET tools. You can install this update from inside the tools themselves, through the Toolbox App, or on our website.
Here’s what’s new in this update.
Rider 2026.2.2 #
AI Agent Setup widget
We’ve recently added a wide range of features to help you work with coding agents in Rider. With so much new functionality, keeping track of every announcement and discovering what’s available can be a challenge. That’s why we’ve now put everything you need in one place.
Rider 2026.2.2 introduces the AI Agent Setup widget, a new entry point in the bottom-right status bar. This new tool helps you find and set up Rider’s features for coding agents. When you open it, you’ll see a list of supported features like MCP tools, skills, and hooks, along with brief explanations of how each one can help your workflow.
The overview shows you which features are already enabled and which ones you can set up, with direct links to the right settings pages. No matter if your coding agent runs inside Rider or in an external terminal, the widget helps you see what Rider offers and quickly find the settings you need to begin.
Less noise and clearer context for AI agents with hooks
Rider’s hooks now provide AI agents with more targeted feedback after code changes. This helps cut down on unnecessary information and makes formatting changes coming from the IDE easier to spot.
Agents now get inspection results from the Run files inspections hook only for the code they added, not the whole file. This lets them focus on their own changes.
The Reformat file hook now gives a diff that shows any formatting changes made by the IDE. Agents can see what changed right away, so they don’t have to reread the file to understand the updates.
Test coverage gets TUnit support
Rider’s dotCover integration now measures coverage for unit tests written with TUnit. To enable coverage, install the JetBrains.dotCover.Framework package in your project.
To enable full Testing Platform support in Rider, go to Settings | Build, Execution, Deployment | Unit Testing | Testing Platform and check the Enable Test Platform support box.
Note: TUnit coverage requires Microsoft.Testing.Platform version 2.3.0 or later.
Notable fixes
Here are some important fixes included in this release:
- RIDER-142337 On macOS 26.2.2, Rider could freeze indefinitely, usually while a large solution, but sometimes at other times. Rider collects thread dumps from its backend process to help diagnose slowdowns. This process briefly suspends the backend and then resumes it. A change to the macOS system API broke the resume step, leaving the backend permanently suspended. This issue has been fixed, and macOS 26.2.2 is now fully supported.
- RIDER-142279 TheAttach to Unity Editor feature no longer depends on the editor executable name. This change fixes problems with recent Unity Hub versions and custom engine builds.
- RIDER-139586 MCP server access errors on attached folders. File operations now work across all folders attached to the solution, not just in the main solution directory.
To see the complete list of fixes and improvements, please visit this page.
ReSharper 2026.2.2 #
Test coverage gets TUnit support
dotCover now measures coverage for unit tests written with TUnit. To enable coverage, install the JetBrains.dotCover.Framework package in your project.
To enable full Testing Platform support in Rider, go to Extensions| ReSharper | Options | Unit Testing | Testing Platform and check the Enable Test Platform support box.
Note: TUnit coverage requires Microsoft.Testing.Platform version 2.3.0 or later.
For the complete list of updates included in this build, please see the full release notes. You can download the latest builds from our website or via the Toolbox App. You can also update Rider as a snap package. Let us know how the new features fit into your workflow in the comments below.