0

I am having problems with CodeLens after installing R# and I would appreciate any help I could get.

After installing Resharper CodeLens stopped showing Telemetry, I should be seeing something like this:

enter image description here

Instead I get a broken Work Item list:

enter image description here

I tried uninstalling Resharper but it wont solve the problem, after reinstalling VS I got telemetry back but I installed Resharper again and the same thing happened.

Resharper is set to not disable CodeLens and all CodeLens options are enabled:

enter image description here enter image description here

I have two accounts connected but Application Insights does not recognize my account for telemetry:

enter image description here

enter image description here

I have confirmed the problem on two other machines.

Versions:

VS: 15.6.3

R#: 2017.3.3

Rodrigo Rodrigues
  • 108
  • 8
  • eric got your version #'s and will check it out. Aside: i'd *uncheck* any codelens indicators you don't actively use. not only does it prevent some of them from doing work you dont need, it also frees up keyboard shortcuts for the others, since they are ALT+0 - ALT+9 (not sure VS has extended that to more than 9), and the shortcuts are assigned in the order they show in that list and are enabled, so that the same shortcut always applies to the same indicator – John Gardner Mar 23 '18 at 23:47
  • is "team coding" a resharper one? maybe try disabling that one and see if things start working again? – John Gardner Mar 23 '18 at 23:47
  • After last night update (15.6.4) team coding does not show as an option, IntelliTrace seems to have replaced it. I tried to leave all disabled and only enabled the App Insights options but it still does not work. – Rodrigo Rodrigues Mar 25 '18 at 01:40
  • 1
    does it only happen the first time you open the first solution after opening VS? we've found a case where now that our package has been converted to a VS "async" package, we get loaded AFTER the solution is loaded and don't get told that, so the extension doesn't know a solution is loaded and doesn't try to do anything with codelens. – John Gardner Apr 02 '18 at 23:02
  • Yes, I believe you perfectly isolated the issue, if I open another solution (or the same solution), close the solution but not VS and open the solution again all work as expected – Rodrigo Rodrigues Apr 03 '18 at 04:26

1 Answers1

1

This is a problem in the loading of the solution, as noted in the comments by VS team, a simple workaround is to close the solution (but not VS) and open again.

Rodrigo Rodrigues
  • 108
  • 8