Resharper stopped working after trial period expiring warning

Resharper 7.1.1 was working fine until the trial period box showed up ~15 days after installed. I am licensed and just forgot to enter the details when I first installed.

After the trial warning, I get no resharper functionality at all: no enhanced Intellisense, nothing in the gutter on the right warning with lines for warnings and errors. I then repaired the Resharper install, and that did nothing. I entered my license info, and it's still gone.

How do I get Resharper functionality back?

There is a RESHARPER menu in VS 2012, so the plugin is definitely present.

6 comments
Comment actions Permalink

Hello Aren,

The description you provided indicates, that somehow a proper integration between ReSharper and Visual Studio is broken.

1. Is it happening for every project/solution you are working with? Have you tried to create new solution and check in ReSharper is wokring fine there?
2. Is ReSharper menu entry in main menu active? Is it working? Like, can you use 'Go To Symbol', or at least open 'ReSharper | Help | About JetBrains ReSharper' dialog?

I would appreciate any detailed information regarding this matter. Some screenshots of what's happening are also apreciated.
Thank you!

0
Comment actions Permalink

Is it happening for every project/solution you are working with? Have you tried to create new solution and check in ReSharper is wokring fine there?


It appears to work fine with a new project, so maybe it's limited to this one project/solution?

Is ReSharper menu entry in main menu active? Is it working? Like, can you use 'Go To Symbol', or at least open 'ReSharper | Help | About JetBrains ReSharper' dialog?


RESHARPER > Help > About JetBrains ReSharper... shows the About JetBrains ReSharper dialog. RESHARPER > Navigate > Go To Symbol pulls up a small dialog with Enter symbol name: on the top left.
0
Comment actions Permalink

Hello Aren,

If the issue seems to be a solution-specific case, please try to remove the '<solution_name>.suo' file and '_<solution_name>.ReSharper' folder (located in the root directory of your current solution) and check if it helps to resolve the issue.

Thank you.

0
Comment actions Permalink

If the issue seems to be a solution-specific case, please try to remove the '<solution_name>.suo' file and '_<solution_name>.ReSharper' folder (located in the root directory of your current solution) and check if it helps to resolve the issue.


Thank you. I found the .suo file and removed it. There is no _solution_name.ReSharper folder.

Removing the .suo file appears to have fixed it. Is this due to a bug?
0
Comment actions Permalink

Not really. *.suo file contains solution- and projects settings in there, ReSharper stores some of its config files there as well. Sometimes, for some reasons, suo file cannot be updated to a newer version (like, when there are no permissions to edit it), so ReSharper fails to do its activity with the old settings.

When this file is removed, VS recreates it on the next solution startup with new configuration.

It is more of a known behavior rather than a bug. However, if you notice any kind of repro scenatio when this issue happens, please let us know.
Thanks in advance!

0
Comment actions Permalink

Sure. In this case, I can assure you that filesystem ACLs would not have prevented writes to the file.

0

Please sign in to leave a comment.