ReSharper C++ don't work
Hi,
I'm using Visual Studio 15.7.6 with ReSharper 2019.3.1 and ReSharper C++ 2019.3.1 (both are licensed and turned on).
I am using this configuration for about a month and everything was working fine. Yesterday I've noticed that something is wrong - ReSharper works dine for C#, but it doesn't work for C++ (it looks like ReSharper doesn't see C++ components). I've noticed it when I wanted to run tests and ReSharper didn't discover any C++ tests. Also other features doesn't work (for example: renaming, code styling).
I've tried to reinstall Visual Studio and ReSharper, clean cache files, disable Read project properties asynchronusly and run ReSharper with trial license. Nothing of this helped. I've also tried to open different projects and effect was the same.
I've uploaded log file from ReSharper: resharper_log_draczka.txt
Please sign in to leave a comment.
Hello,
thank you for contacting us.
Please check that ReSharper C++ is turned on in ReSharper | Options | Environment | Products & Features.
After it, please run Visual Studio with the following command line: 'devenv /ReSharper.LogFile C:\log\resharper_log.txt /ReSharper.LogLevel Verbose'.
Try to reproduce the issue (open C++ project, try to invoke rename, etc) and upload a file via https://uploads.services.jetbrains.com/ form and let us know the exact file name.
Thank you.
Hi,
I've checked ReSharper | Options | Environment | Products & Features and ReSharper C++ is turned on.
I've reproduced issue, created log file and uploaded it (resharper_log_draczka_05.02.2020.txt)
Hi,
thank you for the answer.
Please do follow in internal mode:
- enable 'C++ caches' in ReSharper | Options | Logging;
- open solution;
- send us log file.
Thank you
Hi,
to run ReSharper in Internal mode please start Visual Studio with the "/ReSharper.Internal" command-line argument.
Hi,
I've uploaded log file (JetBrainsLog.JetBrains.2020-02-05T13-02-17.devenv#16404.log)
Hello,
Thanks for the logs. Sorry, but we're still not sure what's happening. I'll try adding more logging in a 2020.1 EAP build and we can try to narrow it down.
One unlikely thing that might cause this is that R++ tries to run an external command on startup to get the list of include directories. If this command hangs, it might lead to the issue you're seeing. Could you please check that if you run
from the command line it finishes successfully?
One other thing which might help - could you please also record a timeline trace for ~10-20 seconds after solution open and send it to us? It might give us some insight into what's happening. The instructions are at https://resharper-support.jetbrains.com/hc/en-us/articles/210652849-Collect-Timeline-performance-snapshot-in-Visual-Studio.
Thanks a lot!
Hi,
I've taken and uploaded a snapshot from Visual Studio. I've also send log from running requested command (VsDevCmd_draczka_06.02.2020.txt)
Hi,
I've uploaded log from running command
once again. Previous wasn't properly executed (VsDevCmd_draczka_06.02.2020_2.txt)
Have you got any update on my case?
I have fixed my issue using solution from this site: http://doc.fireflymigration.com/build-error-vsvars32.bat-editbin.html
Sorry, I'm not sure I understand - are you saying that "Desktop development with C++" was not installed in your VS2017 setup?
Yes. We have created custom VS installation settings, which contained only selected packages (it was enough to build solution). During first installation I've installed VS with all C++ related packages and everything was working. Then I had to reinstall VS and I have used our custom installation settings and the problem with ReSharper occured.
Interesting, thanks. Looks like the command hangs for some reason when "Desktop development with C++" is not installed. I'll try to reproduce.
Here is a screenshot with our VS installation setup.
I recreated this configuration and everything is still fine on my side. Sorry, I missed a set of quotes last time - could you please run this command once again from the command line and check if it hangs?
On my machine it prints
As I checked old log - the command was ending, but it ended with message:
Now it ends with printing
Thanks! I thought this command would hang for some reason, but it seems to run ok. As I mentioned, I'll try to add more logging to better diagnose what's happening in future builds, as of now I have no good ideas.