Share via

Codelens references not showing in Visual Studio Professional 2015 with Updates - "Microsoft.Alm.Shared.Remoting.Remotecontainer.dll has stopped working"

  • Article

Question

Thursday, January 25, 2018 12:09 PM

Hello, Internet.

Any time I open a solution with Codelens turned on (even just the bare bones version that counts references), I get a message that the .dll in the title has stopped working.

This results in references showing as "- references" while other features of Codelens (if toggled on) keep functioning as normal.

Things that I have tried in order to fix the issue:

  1. Resetting all settings in Visual Studio Professional 2015 with Updates (Tools --> Import and Export Settings --> Reset all settings)
  2. Performing a Repair on Visual Studio Professional 2015 with Updates by way of the Windows 10 control panel.
  3. Performing an uninstall (standard Windows 10 way) and reinstall of Visual Studio Professional 2015 with Updates
  4. Performing a complete uninstall (using Microsoft's own Total Uninstaller) followed by a reinstall of Visual Studio Professional 2015 with Updates

Yet the problem persists.

*Some slight clarification on the crash of the .dll: It seems that the Microsoft.Alm.Shared.Remoting.Remotecontainer.dll only crashes when a reference count is attempted by Codelens. I.e. if I launch my solution and open a .cshtml as the first item (codelens does not attempt to count references here), I do not get the crash, but as soon as I navigate to a .cs file with methods and properties, Codelens attempts the reference count, and the .dll promptly crashes, every time.

Does anyone out there have any ideas? Because I am out.

All replies (3)

Friday, January 26, 2018 6:18 AM | 1 vote

Hi bjornlaursen,

Welcome to the MSDN forum.

Did you meet this issue for the specific solutions or all solutions?

Refer to your description, I found a similar issue: CodeLens not showing references

If only the specific solutions have this issue, please have a try with the following to troubleshoot this issue:

  1. Check there have circular references in your solution or not
  2. Close this solution and delete the hidden .vs folder under the solution store folder

If not, please try the methods as below:

  1. Go to Tools -> Options... -> Text Editor -> All Languages -> CodeLens, uncheck and check this option
  2. Close all programs and clean C:\Users{user}\AppData\Local\Temp folder
  3. Modify the VS 2015 and check the component “Git for Windows (3rd party)” to install
  4. Check if the firewall blocks it or not

Best regards,

Sara

MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected]

Friday, January 26, 2018 7:57 AM

Hi Sara,

Thanks a lot for replying.

It is indeed all solutions that I have this problem in, so it seems to be related to Visual Studio itself.

Going by your four point list:

  1. Tried it, no effect.
  2. Just did it now, no effect.
  3. Had not tried this, since it seems very unrelated, but I gave it a go and to my despair, it had no effect.
  4. Again, to me it seemed unrelated, but I wrote our local IT dept., and they confirmed that the .dll is not being blocked by a firewall.

Some slight clarification on the crash of the .dll: It seems that the Microsoft.Alm.Shared.Remoting.Remotecontainer.dll only crashes when a reference count is attempted by Codelens. I.e. if I launch my solution and open a .cshtml as the first item (codelens does not attempt to count references here), I do not get the crash, but as soon as I navigate to a .cs file with methods and properties, Codelens attempts the reference count, and the .dll promptly crashes, every time.

Tuesday, January 30, 2018 8:58 AM

Hi bjornlaursen,

Thank you for your update and sorry for my delay reply. If you try to create a new project and does this issue persists or not?

Does this issue occurs after your initial VS 2015 installation or it just happen recently?

Best regards,

Sara

MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected]