{"id":646243,"date":"2025-10-02T14:41:41","date_gmt":"2025-10-02T13:41:41","guid":{"rendered":"https:\/\/blog.jetbrains.com\/?post_type=dotnet&p=646243"},"modified":"2025-10-03T08:23:28","modified_gmt":"2025-10-03T07:23:28","slug":"resharper-and-visual-studio-2026","status":"publish","type":"dotnet","link":"https:\/\/blog.jetbrains.com\/en\/dotnet\/2025\/10\/02\/resharper-and-visual-studio-2026","title":{"rendered":"ReSharper and Visual Studio 2026: Day-One Compatibility, Migration Steps, and Performance Gains"},"content":{"rendered":"\n

Microsoft Visual Studio 2026 Insiders<\/a> is here, and the next major VS update is on the horizon. As with any new Visual Studio version, one of the first questions developers ask is: “Will my extensions work after updating \u2013 especially ReSharper?”. <\/p>\n\n\n\n

The short answer is a resounding \u201cyes\u201d. But there’s more to the story, and we suspect you’ll want to know how both Microsoft and JetBrains worked together to ensure ReSharper supports your development with Visual Studio 2026 from day one. If that sounds good, keep reading.<\/p>\n\n\n\n

What works today<\/h2>\n\n\n\n

To help ensure a smooth day-one experience, we coordinated with the Visual Studio team and tested ReSharper on Visual Studio 2026 Insiders. ReSharper 2025.2.1 was validated for compatibility and ready to use with Visual Studio 2026 Insiders as soon as it released. <\/p>\n\n\n\n

Visual Studio 2026 Insiders also supports side-by-side installation with VS 2022, so you can try the preview without replacing your current setup. Most VS and ReSharper settings are carried over; if you use custom profiles, make sure to review them after installation. <\/p>\n\n\n

\n
\n Download ReSharper for VS 2026 Insiders<\/a>\n <\/div>\n <\/div>\n\n\n\n\n\n\n\n

Microsoft\u2019s new migration strategy<\/h2>\n\n\n\n

One of the significant changes in Visual Studio 2026 is Microsoft\u2019s new approach to extension compatibility. For the first time, the IDE is backward-compatible with extensions built for VS 2022<\/a>, meaning most tools will migrate automatically.<\/p>\n\n\n\n

In earlier releases, extension developers often had to ship dedicated builds targeting each new VS version, which sometimes created gaps in support. With VS 2026, those friction points are gone.<\/p>\n\n\n\n

For developers, this is great news: you don\u2019t have to abandon essential tools when you upgrade to Visual Studio 2026. However, for ReSharper, the new migration scheme initially presented an unexpected challenge. <\/p>\n\n\n\n

ReSharper installer and Migration Assistant<\/em><\/h2>\n\n\n\n

During early testing, we saw that the new extension migration flow was primarily designed for .vsix<\/code>-based extensions, which are the most common type. Because ReSharper uses an .exe<\/code>-based installer, it doesn\u2019t automatically take advantage of that flow. <\/p>\n\n\n\n

Switching to a different type of installer might seem like the obvious choice until we examine why ReSharper chose a different path in the first place. Using an .exe<\/code>-type installer allows us to ship standalone .NET tools, such as dotTrace, dotMemory, dotPeek, and dotCover, that complement ReSharper\u2019s functionality. It also makes ReSharper expandable through its own plugins<\/a> \u2013 something that regular .vsix<\/code> plugins aren\u2019t capable of. <\/p>\n\n\n\n

Not willing to risk leaving our users without ReSharper support around the release of .NET 10 and the latest updates to C#, we started to rethink our installation flow in the new environment. We came up with the idea of a .vsix<\/code> extension that would serve as a bridge between the two versions of Visual Studio. And thus, the Migration Assistant<\/em> was born.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Starting with ReSharper 2025.2.2, the Migration Assistant<\/em> can be installed into Visual Studio 2022 from the Visual Studio Marketplace<\/a>. For your convenience, we also bundled it with ReSharper. When installed, this lightweight extension will be covered by the new migration flow, ensuring smooth transitions both now and in the future.<\/p>\n\n\n\n

How to migrate ReSharper to Visual Studio 2026<\/h2>\n\n\n\n

To make sure ReSharper comes along when you upgrade to VS 2026, follow these simple steps:<\/p>\n\n\n\n

    \n
  1. Install ReSharper 2025.2.2 or later into Visual Studio 2022.<\/li>\n\n\n\n
  2. Check the Visual Studio Extension Manager<\/em> to make sure you have ReSharper Migration Assistant <\/em>installed. <\/li>\n\n\n\n
  3. When upgrading to Visual Studio 2026, select Include installed extensions from the Visual Studio Marketplace <\/em>from the installation dialog.<\/li>\n<\/ol>\n\n\n\n
    \"\"
    Select “Include installed extensions from the Visual Studio Marketplace” to enable the migration of ReSharper and other extensions into Visual Studio 2026. <\/em><\/figcaption><\/figure>\n\n\n\n
      \n
    1. Launch Visual Studio 2026, and go to Extensions | ReSharper Installer | Install ReSharper.<\/em><\/li>\n<\/ol>\n\n\n\n
      \"\"<\/figure>\n\n\n\n

      The familiar dotUltimate installer will pop up and allow you to configure the desired set of tools for your setup. After the installer completes and you restart Visual Studio, ReSharper will be ready to use in the new IDE. <\/p>\n\n\n\n

      Our plan for future releases is to make this final step completely automatic. We believe you deserve a truly seamless experience when it comes to ReSharper’s coverage across different versions of Visual Studio, and we’re committed to making that happen.<\/p>\n\n\n\n

      Advancing together <\/h2>\n\n\n\n

      Visual Studio 2026 includes performance work from the Visual Studio team, aimed at faster solution loading and a more responsive UI. Early reports point to faster solution loading. Note:<\/em> Results can vary by codebase and environment. For example, one published case study reports a drop from 14 seconds in VS 2022 to about 9 seconds in VS 2026<\/a>. Microsoft attributes this to optimizations that reduce UI thread work and increase asynchronous operations. <\/p>\n\n\n\n

      JetBrains has also been addressing the performance aspect from our side. In the ReSharper 2025.2 release, we introduced Out-of-Process<\/em> (OOP<\/em>) mode. When enabled, it allows ReSharper to run its analysis engine in a separate process, so heavy tasks like indexing or inspections don\u2019t cause your IDE to freeze. In our measurements, working out of process reduced the number of Visual Studio 2022 startup UI freezes by 61%<\/a>. And that\u2019s just one of the more prominent improvements done for the latest release. You can learn more about ReSharper\u2019s recent refactorings and performance gains here<\/a>.<\/p>\n\n\n\n

      Together, these improvements mean that Visual Studio 2026 and ReSharper truly complement each other, making the overall experience feel more responsive, especially on large solutions. <\/p>\n\n\n\n

      Wrapping up<\/h2>\n\n\n\n

      If you’re exploring Visual Studio 2026 Insiders, make sure that you have ReSharper 2025.2.2 or later installed. Take a moment to install the Migration Assistant<\/em> from the Visual Studio Marketplace \u2013 it takes less than a minute and ensures ReSharper will be there when you upgrade. <\/p>\n\n\n

      \n
      \n Install Resharper<\/a>\n <\/div>\n <\/div>\n\n\n\n\n\n\n\n

      We’re excited about what Visual Studio 2026 brings to the table, and we’re committed to making sure ReSharper continues to enhance your development experience across every version of Visual Studio. If you encounter any issues or have feedback to share, please let us know through our issue tracker<\/a> or support channels.<\/p>\n","protected":false},"author":1337,"featured_media":646278,"comment_status":"closed","ping_status":"closed","template":"","categories":[4992,89,3990],"tags":[6286,2863,46,8936,8937],"cross-post-tag":[6639],"acf":[],"_links":{"self":[{"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/dotnet\/646243"}],"collection":[{"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/dotnet"}],"about":[{"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/types\/dotnet"}],"author":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/users\/1337"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/comments?post=646243"}],"version-history":[{"count":10,"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/dotnet\/646243\/revisions"}],"predecessor-version":[{"id":646438,"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/dotnet\/646243\/revisions\/646438"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/media\/646278"}],"wp:attachment":[{"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/media?parent=646243"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/categories?post=646243"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/tags?post=646243"},{"taxonomy":"cross-post-tag","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/cross-post-tag?post=646243"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}