Support for Visual Studio 2022

Great work. Running R# in VS2022 64bit is really nice, as lots of lags caused by memory pressure are gone now.

There is a minor timing issue when starting VS2022 (Preview 3.1) and opening the first solution. We use SWEA, so after the solution opened, SWEA starts to analyze the files - and shows lots of unknown symbols. As a workaround, you can run "Restore NuGet packages" manually on the solution. This does not restore anything, because all files are already there, but it makes R# to detect possibly NuGet and assembly changes and reload details. And after that, SWEA is able to resolve symbols correctly. So I think that SWEA should wait for the first assembly processing or NuGet update before it starts to report errors about unknown symbols.

What happened to the Check for Updates menu items? I just checked dotPeek and Resharper and the menu item is missing from both Help menus.

Hello Jlavallet,

This item was moved intentionally. We'll publish a new preview build for VS 2022 separately and announce it in our blog and update this page as well.

Thank you.

Hello Carsten Schuette,

thank you for the feedback. 

Could you please specify if you experience this problem for any solution in VS 2022 + ReSharper?

Does it happen in other VS versions?

Thank you.

I'm seeing a weird issue in VS 2022 Preview 3.1.

In a C# file with lots of collapsed regions, only random ones are displaying the region text, all the others show "...". The problem goes away when I disable R#.

I also noticed that when using ALT+UP to move a block of code, the block will scroll to the top and then I can't see where it's going. The problem goes away when I disable R#.

Hi Angelina Elycheva, the issue occurs with several solutions. I am very sure that this issue is not completely new to VS2022, but in older versions, SWEA takes more time to start because it often brins VS2019 into memory problems.

Hello Keith,

Sorry I've missed your comment about the problems you are experiencing.

Concerning the problem with regions, could you please provide some screenshot demonstrating the issue?

As for Alt+Up shortcut, it's a known issue that doesn't depend on VS version, you are welcome to follow it - https://youtrack.jetbrains.com/issue/RSRP-480634.

Thank you.

I hope we will see a new version this week since the last expire after a week ;)

Otherwise, current version works very well in VS2022 Preview 3

Hello Sviataslau Hankovich,

Please try workaround suggested here - https://youtrack.jetbrains.com/issue/RSRP-485314#focus=Comments-27-5084082.0-0 and let me know if it helps.

Thank you.

Hi Angelina Elycheva, I tried and it helped for the described case, but it fails for hints inside the existing code;

After pressing TAB:

After pressing TAB one more time:

Does this have new features or is it just a 30-day extension?

Hello Simon! It's just a 30-day extension. What new features do you expect?

I guess he's asking if there are any bug fixes included in this release?

I was hoping that the File-scoped namespaces feature mentioned higher up would be included plus bugfixes so far.

What new features do you expect?

I don't care about "new features", but there are a number of bugs to do with VS and R# fighting (overlapping pop-up lists, intellicode completion) which I rather hoped were going to be sorted.

Count me disappointed that nothing's been done towards fixing this stuff in the last month.

I think I misused the phrase "new features" - I meant bugfixes/C# 10 support/other issues marked as Fixed in  YouTrack etc.

Hello Sviataslau Hankovich,

added the specified case as a comment to the corresponding issue.

Thank you for the feedback.

I updated, but it says "Free trial period will expire tomorrow" in License Information.

Update: It says my free trial has expired and I need to buy it, even though I updated.

Leo Holdiman we are working on a fix. I hope the new build will be delivered today. My apologies for the inconvenience. 

So, I've just uploaded the new build (JetBrains.ReSharper.2021.2.EXP02.Checked.exe) and updated the URL in the article. Now the build has a new 30-day trial period.

In the previous build, we reset an expiration date (aka a time-bomb) only but didn't touch the trial period timer. Most of the users, who activated the build using a ReSharper license, didn't notice that. It affected only people with a trial period as an activation way. 

Apologies for the inconvenience. 

I thought you changed the policy for EAP builds to require licenses?

Thanks to everyone working on that.

For an EAP Beta Unstable build this works great - and performance-wise, this is a great step forward. I'm really looking forward to the final product. 

Stupid question, but what about an offline installer for the Resharper (Ultimate) 2020 preview? Can't see it on the "other versions" page :)

EDIT: It's an offline installer! I just don't realized it! Got help from Maarten on twitter :) 

Hello Jlavallet,

Error list shown below is VS error list, not ReSharper one. 

A fair point but it's a little pants that it says it's going to put one thing and then put something else by default. :-)

Meric Stanley Please try this workaround https://youtrack.jetbrains.com/issue/RSRP-485314#focus=Comments-27-5084082.0-0. Thanks! 

Hi Alexander - that workaround doesn't work for me (most of the time), and I've also applied the other two suggestions in that thread.  

@... Please comment on this YouTrack issue and describe in detail what you've tried and what you still have. My colleagues will investigate it.