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.

 

Update from 12.11.2021

The latest EAP build supports the release build of Visual Studio 2022! 

You can download the latest ReSharper 2021.3 EAP here:

Download ReSharper 2021.3 EAP

95 comments
Comment actions Permalink

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

0
Comment actions Permalink

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.

0
Comment actions Permalink

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

 

0
Comment actions Permalink

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.

Edited by Angelina Elycheva
3
Comment actions Permalink

Hello Sviataslau Hankovich,

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

Thank you for the feedback.

0
Comment actions Permalink

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.

Edited by Leo Holdiman
0
Comment actions Permalink

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

0
Comment actions Permalink

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. 

0
Comment actions Permalink

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

0
Comment actions Permalink

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. 

0
Comment actions Permalink

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 :) 

Edited by Johan Danforth
0
Comment actions Permalink

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

 

1
Comment actions Permalink

Hello Jlavallet,

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

0
Comment actions Permalink

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?

1
Comment actions Permalink

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

1
Comment actions Permalink

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. :-)

0
Comment actions Permalink

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.  

 

0
Comment actions Permalink

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.

1
Comment actions Permalink

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

Edited by Alexander Kurakin
0
Comment actions Permalink

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

1
Comment actions Permalink

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! 

Edited by Alexander Kurakin
1
Comment actions Permalink

I just received

when creating a new WPF application.

0
Comment actions Permalink

Hi, is VS 2022 Preview 4.1 supported now?

0
Comment actions Permalink

Michael Schreiber, if you notice any performance problems, then please collect some additional information about it for us using the following steps. Thanks in advance!

Aka Tirexx, there are some issues with competition, but yes, ReSharper should work in 4.1.

0
Comment actions Permalink

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.

 

1
Comment actions Permalink

Carsten Schuette, I see that you also submitted a support request about this issue, thank you! We're looking at it and will get back to you shortly.

Edited by Maria Pleskunina
0
Comment actions Permalink

Using ReSharper 2021.3 EAP 2 and it is recognizing implicit usings (greyed out) but the fix doesn't do anything (singly via Alt-Enter or Remove Unused Directives in Project).

Is this supposed to be working?

0
Comment actions Permalink

Hello Simon Hewitt,

The fix of this issue will be available in the next EAP3 build, which we are going to release within a few weeks. 

Thank you.

0

Please sign in to leave a comment.

Have more questions?

Submit a request