R# w vs2022 issues

First problem:

* Sometimes R# appears to be disabled. It doesn't respond to keyboard commands and doesn't the show light bulb icon. Closing then reopening the affected file usually brings it back.

* I had one case where I opened a solution then opened program.cs and VS2022 just removed itself from the desktop. When I restarted VS it suggested disable R#.

* R# seems unable to run unit tests. It threw an exception that I've reported by the exception tool.

Anyway I'm going back to vs2019 now. I'll try vs2022/R# at some future date.

17 comments
Comment actions Permalink

Hello,

thank you for the feedback.

Could you please specify what VS 2022 version you are using?

The first two issues seem to be tricky ones, we are not aware of such problems. Is there any chance you could reinstall ReSharper for VS 2022 and help us to troubleshoot the problems?

The last one concerning tests, do you mean running test or debugging? There's a known problem with debugging.

Thank you.

0
Comment actions Permalink

This was using the latest VS 2022 preview (#5 I think, only recently released). This was my first serious attempt to move to vs 2022 so I upgraded everything before the weekend.

The first time I tried to run tests the code compiled but nothing else happened. The second attempt was almost the same but this time an exception was logged which I've raised using the dynamic analysis tool.

 

I will re-install R# later this week and see what happens.

0
Comment actions Permalink

Thank you for the reply and your assistance.

Please submit any issue you experience and we'll investigate it.

0
Comment actions Permalink

Hmm. It's happening with vs 2019 this morning as well. It appears to be caused by DEXP-625533.

0
Comment actions Permalink

Could you please specify what steps caused this expectation?

Thank you.

0
Comment actions Permalink

I typed the name of a field and R# didn't offer anything. So I tapped Ctrl+Space and that exception occurred. R# still didn't respond. All of this happened after I launched vs 2022 so I'm wondering if the caches have been corrupted by different versions. It seems odd that it should suddenly start doing it.

0
Comment actions Permalink

Do I understand correctly that VS got freezed after Ctrl+Space? Is it possible for you to reproduce the issue and provide a dump as described in the following help article - https://resharper-support.jetbrains.com/hc/en-us/articles/206546619.
Thank you.

0
Comment actions Permalink

Okay, it's not the cache. It seems that there's something broken with R#. I've attached a video. Note that R# is unable to offer any help with the identifier 'repeatInstruction' until I actually type it out at which point it seems to suddenly wake up and realise what's going on:

https://recordit.co/fzwum12WQV

 

0
Comment actions Permalink

..and five minutes later R# just stopped responding to the keyboard or the gutter icon until I changed to a different file and then back. Whatever the cause it my R# appears to be in a bad way since applying the vs 2022 Preview 5 update and it's even affecting vs 2019.

0
Comment actions Permalink

Could you please start VS with the following command: ``devenv.exe /ReSharper.LogFile C:\log\resharper_log.txt /ReSharper.LogLevel Verbose``, reproduce the issue and send us resharper_log.txt. You can share it privately via https://uploads.jetbrains.com/ and let me know upload ID.

Thank you.

0
Comment actions Permalink

I'll do that tomorrow. I will bounce my machine over night.

0
Comment actions Permalink

I'm about to restart VS as per your above instructions but I've already noticed that sometimes R# is not updating its database when a file is changed. It seems to happen randomly and saving the modified file usually clears it. This time I've cleared the caches and restarted my machine.

0
Comment actions Permalink

Restarted VS and got the issue immediately so you're in luck. ID is 2021_10_21_TMYfWXvRaF1V1A4A.

R# isn't responding to my defined shortcut (Ctrl+F12, the default Ctrl+Shift+T nor the menu item 'Goto File'. The log file is vaguely informative:

10:18:40.504 |V| RdActions | :1 | Started 'GotoFile' action. Attempt: 1.
10:18:41.052 |V| OneOfaListActionHandler | :1 | Unsubscribing escape handler: JetBrains.Application.UI.PopupLayout.PopupWindowContextSpecificEscapeActionHandler
10:18:41.065 |V| GotoSearchController | :1 | Clearing caches.
10:18:41.073 |V| RdActions | :1 | 'GotoFile' Action execution session is terminated (by frontend possibly).
10:18:46.896 |V| RdActions | :1 | Started 'GotoFile' action. Attempt: 1.
10:18:46.921 |V| OneOfaListActionHandler | :1 | Unsubscribing escape handler: JetBrains.Application.UI.PopupLayout.PopupWindowContextSpecificEscapeActionHandler
10:18:46.922 |V| GotoSearchController | :1 | Clearing caches.
10:18:46.923 |V| RdActions | :1 | 'GotoFile' Action execution session is terminated (by frontend possibly).
10:18:47.425 |V| RdActions | :1 | Started 'GotoFile' action. Attempt: 1.
10:18:47.434 |V| OneOfaListActionHandler | :1 | Unsubscribing escape handler: JetBrains.Application.UI.PopupLayout.PopupWindowContextSpecificEscapeActionHandler
10:18:47.434 |V| GotoSearchController | :1 | Clearing caches.
10:18:47.435 |V| RdActions | :1 | 'GotoFile' Action execution session is terminated (by frontend possibly).
10:18:47.682 |V| RdActions | :1 | Started 'GotoFile' action. Attempt: 1.
10:18:47.699 |V| OneOfaListActionHandler | :1 | Unsubscribing escape handler: JetBrains.Application.UI.PopupLayout.PopupWindowContextSpecificEscapeActionHandler
10:18:47.700 |V| GotoSearchController | :1 | Clearing caches.
10:18:47.701 |V| RdActions | :1 | 'GotoFile' Action execution session is terminated (by frontend possibly).
10:18:47.865 |V| RdActions | :1 | Started 'GotoFile' action. Attempt: 1.
10:18:47.886 |V| OneOfaListActionHandler | :1 | Unsubscribing escape handler: JetBrains.Application.UI.PopupLayout.PopupWindowContextSpecificEscapeActionHandler
10:18:47.886 |V| GotoSearchController | :1 | Clearing caches.
10:18:47.887 |V| RdActions | :1 | 'GotoFile' Action execution session is terminated (by frontend possibly).

0
Comment actions Permalink

Having returned to VS after uploading the log and posting the above comment GotoFile is now working again. Second log attached:

2021_10_21_MLYmpV2VJDQNJgfr

0
Comment actions Permalink

It currently seems very reproducible. After I stop debugging R# stops responding to events unless I switch the focus away and back.

0
Comment actions Permalink

Despite restarting my computer it is still completely reproducible. If the debugger stops on encountering an exception R# is effectively disabled until I clear the exception window and switch focus away from VS 2022 then back again.

0
Comment actions Permalink

Hello Aruecope

Unfortunately, there's seems to be nothing interesting in the log files.

Could you please let me know if the problem is reproduced in some specific solution only? Is it reproduced in a newly created solution?

Thank you.

0

Please sign in to leave a comment.