Support for Visual Studio 2022 Preview

Update from 29.09.2021

Finally, we decided to push this support to the 2021.3 release cycle. The first EAP build of v2021.3 has already had the VS2022 Preview support included. There is no need to download and install a separate build to run ReSharper in VS2022 Preview builds – just select the VS2022 Preview icon in the dotUltimate 2021.3 EAP installer. You can download the latest ReSharper 2021.3 EAP here:

Download ReSharper 2021.3 EAP

66 comments
Comment actions Permalink

It still works with VS2022 preview 3 😉

9
Comment actions Permalink

Thanks for letting us know Pascal Craponne I just updated and was asking myself

0
Comment actions Permalink

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

2
Comment actions Permalink

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.

1
Comment actions Permalink

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.

1
Comment actions Permalink

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

1
Comment actions Permalink

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.

Edited by Carsten Schuette
0
Comment actions Permalink

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.

0
Comment actions Permalink

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.

0
Comment actions Permalink

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.

0
Comment actions Permalink

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#.

0
Comment actions Permalink

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.

0
Comment actions Permalink

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....?

1
Comment actions Permalink

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.

1
Comment actions Permalink

Hello Carsten Schuette,

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

Thank you.

1
Comment actions Permalink

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.

0
Comment actions Permalink
 
Here is a screenshot that shows some of the problems. In this file I was able to clean up some of the visual glitches. But as you can see by the annotations, there is a lot of orphan region indicators as well as small connector lines that are mismatched.
 
The region at the top with "..." is an example of how most of the regions looked before I hit backspace/enter on them to get them to display properly.
 
Edited by Keith
0
Comment actions Permalink

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

0
Comment actions Permalink

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

12
Comment actions Permalink

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

3
Comment actions Permalink

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

 

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

 

1
Comment actions Permalink

Hello everyone,

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

Thank you.

4
Comment actions Permalink

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.

0
Comment actions Permalink

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:

0
Comment actions Permalink

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?

3
Comment actions Permalink

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! 

Edited by Alexander Kurakin
4
Comment actions Permalink

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

0
Comment actions Permalink

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

0
Comment actions Permalink

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

0
Comment actions Permalink

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.  

1

Please sign in to leave a comment.

Have more questions?

Submit a request