Support for Visual Studio 2022

This is working really well, but it only has 7 more days, are we going to get a new preview version?  Because I want to keep using this, its pretty great

It still works with VS2022 preview 3 😉

Hello everyone,

We'll publish a new build for VS 2022 shortly, won't abondon you.

Thank you.

Hey everyone! 

I've uploaded a new build, please download it from the link above in the artcile. It has new 30 days included. 

Also, it officially supports the Visual Studio 2022 Preview 3.1 build.

Thanks! 

hey,

So now that VS2022 is released, when can we expect a full R# support?

2 days left.....i am still wondering where is the release?!

Hello Angelina Elycheva,

Thank you for that you won't abandon us ;)

We wait with impatience the new release. I suppose it will be on this page. Right?

Hello everyone,

We are working on ReSharper 2021.3, which includes new features like C# 10 support, bugfixes etc. It will support VS 2022 by default.

Early Access Program for 2021.3 will be started in a month, while it's not yet opened we suggest using this build for VS 2022.

Thank you.

I've gotten a crash (and told it to submit it) while compiling a big project.

It also doesn't seem to handle file-scoped namespaces:

namespace Foo
{
  public class Bar
  {
  ..
  }
}

Works.

namespace Foo;
public class Bar
{
..
}

Does not work.

"Empty namespace declaration is redundant" and "Namespace body block expected".

Compiles and works without warnings or errors.

.Net 6.0 project.

Visual Studio 17.0.0-preview3.

// Stefan

Wow! This runs sooo smooth.

Tried a couple of project wide refactorings, and it just completed them without the slightest issue, despite using 2.6G Mem for the VS process itself.

Tried opening a aspx file and making an edit... This usually takes 1-2 min for the first edit in vs2019, with this it was barely noticeable. (3.2G mem usage now)

Tried pasting something in a section of 1200 autogenerated lines of code that always wants to reformat after paste... Slight speedup undoing the formatting there, and still running smoothly with 3.8G mem usage and Resharper reporting using 1.4G alone.

Very nice improvements! Will definitely use this all next week and report any bugs I find.

Hello Stefan Smietanowski,

File-scoped namespaces feature is going to be supported in ReSharper 2021.3 version.

Concerning a crash issue, could you please specify if you've got any issue ID once you'd submitted the crash?

Thank you.

Hi Angelina Elycheva, thanx for the fast reply.

I had submitted it, but when I looked right now I saw it was still in pending and not submitted, so I hit the submit privately button again. This time it submitted it.

DEXP-614209

It is submitted using my work account and not my private one. Feel free to contact me outside of here if you want more information, etc.

Regarding the feature not being implemented - I gathered that was the reason. I bet your order of priority is : 1) Get it to run. 2) Add features, as 2 is useless without 1. Same goes for global usings, etc.

Thank you for a great product, I use it daily.

// Stefan

Another issue: During normal work, I can see that VS2022 and R# consumes more and more memory. From about 1,5GB after startup and solution load in the morning to over 6 GB RAM on the afternoon. Older VS2019 crashed because of OOM exceptions, now VS2022 still works fine, but becomes slower over the day.

So, how to take memory snapshots of VS2022/R# and let you analyze where the memory is used....?

Hi Carsten Schuette. I saw something similar with VS2022 (without R#) but it was only default behaviour of 64-bit GC. It simply don't run if you have enough memory. When I attached dotMemory and took snapshot (force GC) it shrinked from 6GB back to 1,5GB.

Hello Carsten Schuette,

Please follow this article  to collect a memory snasphot and send it to JB team.

Thank you.

I've noticed VS hints are shown, but I can not accept them.

but if i'll pres TAB, I'll see 

Alistair Wilson there is nothing new in this build. It's been built from the same sources as the first build we initially published. So, it's just a 30-day extension.  

Johan Danforth The link in the article leads to an offline installer that consists of ReSharper and ReSharper C++. 

Hi R# team, loving the preview. Finding it frustrating that Visual Studio's snazzy new AI autocomplete gives some good suggestions but then R# is overriding the suggestions and putting something else. Any plans to make these work together nicely?

I disabled VS IntelliCode as soon as I could work out how. I thought it was dreadful!

Thanks Alexander Kurakin, a very quick test seems to suggest it does what I expect. I'll add to the ticket if I feel I can contribute anything.

Thanks Alexander - if I can get the same thing to happen twice I will try and add something to the issue!

Hey everyone! 

We've just launched the ReSharper 2021.3 EAP and support for VS2022 Preview is included in the first EAP build. There is no need to download and install a separate build to run ReSharper in VS2022 Preview builds

Thanks! 

EAP1 and EAP2 feel extremely slow compared to the experimental build provided here before. I can see lots of CLR threads consuming one CPU core by calling lots of "clr.dll!LogHelp_LogAsser+0x5ebb" methods.

I kept losing R# keyboard shortcuts. Also occasionally R# just didn't seem to be 'active' for the file I was editing until I closed/reopened the file. I also had a hard crash from vs2022 which on restart it blamed R# for. Lastly R# seems unable to run our unit tests (it through an exception that I reported via the logger).

All in all not a good experience. Tried it for an hour, had to give up and go back to vs 2019.

EAP7 doesn't work for me with the released VS2022. I have just done a repair. Haven't tried to uninstall/reinstall...

ReSharper 2021.3 EAP already provides support of VS 2022, you can find the link in the initial message of this thread. If you are aware of something not working properly please contact us.

ReSharper 2021.3 RTM version will come in a month.

Thank you.

Hello Arman Ghazanchyan

This happens to be a known issue - https://youtrack.jetbrains.com/issue/RSRP-486348. We are working on the fix. The error indicates that some of ReSharper resources were not cleaned up normally and we had to clean them up on going to a suspended state. You may ignore this message box.

Thank you.

Robert Bernstein, thank you for your feedback. Probably this problem is due to the fact that the VS 2022 Preview 2 update broke ReSharper. So far we've made a fix in ReSharper 2022.1 EAP7 only. We hope that soon we will be able to make a bugfix for the 2021.3 version.

Thanks for letting us know @... I just updated and was asking myself