Debugging Visual Studio Add-In


when debugging a Visual Studio Add-In and e.g. changing a breakpoint thru
running debug session you cant go back to your Add-In (showing a sandglas).
Debugger "Break All" command stops every time at:

Line 128 + 0xd bytes C#

Without ReSharper everythings works fine.


1 comment
Comment actions Permalink


>> JetBrains.ReSharper.Shell.dll!JetBrains.ReSharper.Shell.SocketManager
>> .PortListenerThread.Run() Line 128 + 0xd bytes C#

This is a secondary thread that doesn't do anything useful at all. Debugger
prefers to break there probably because it's the only managed frame it can
find at the moment.

What's there on the call stack in other threads?

For debugging the Add-In, you could employ another Visual Studio Hive that
has no R# installed, so that to prevent any side-effects on the part of R#.

Serge Baltic
Omea & R# Developer
JetBrains, Inc —
“Develop with pleasure!”


Please sign in to leave a comment.