2

System in written in C#, .Net4.5. I am trying to remote debug one of our Web APIs. I am using msvsmon.exe (2015) on server and running Visual Studio 2015 on my local.

I can connect to process no problem and breakpoints are being hit, I am also sure I am running same version of code as I manually copied over dll and pdb files from my local machine to the server.

I can't even inspect strings when they are fired into endpoint I get Internal error in the expression evaluator. To remedy this error offered solution is to tick the box on Managed Compatibility Mode in Tools -> Options -> Debugging however, when I do this, when I try to attach to process in debug window, I get unable to attach to the process. the rpc server is unavailable. Solution to which offered is to untick that same box, lol.

I have also tried in vain to enable Use the legacy C# and VB expression evaluators in debug options but that didn't do any good.

I am sure someone by now have ran into this problem.... How do I inspect objects when remote debugging on VS2015?

Community
  • 1
  • 1
Matas Vaitkevicius
  • 58,075
  • 31
  • 238
  • 265
  • 1
    Common question. You've tried all the known workarounds, there aren't anymore. What they basically do is bypass the new VS2015-specific code in the debugging engine. It is very buggy, the price of agile, work on it gets [postponed repeatedly](https://github.com/dotnet/roslyn/issues/9853). All you can do next is call Microsoft Support. Fwiw, you ought to take that RPC error a little more serious. Might well be the underlying problem with the expression evaluator. Environmental issue, disable anti-malware and firewall and whatever other shovelware wants to network. – Hans Passant Nov 03 '16 at 17:00
  • @Matas Vaitkevicius, what about this issue? Could you share us the latest information about this issue? – Jack Zhai Dec 01 '16 at 11:39
  • @JackZhai-MSFT There isn't any information, I simply added insane amount of oldschool logging that writes to text files and solved my issues that way.... – Matas Vaitkevicius Dec 01 '16 at 11:53

1 Answers1

0

I met the error "unable to attach to the process. the rpc server is unavailable" before which was related to the firewall, like Hans Passant's suggestion, you could test it again after you close/disable the firewall or other third party tools. Of course, you could also add your VS Devenv.exe to the Firewall allow list like this thread, debug it again.

https://cerkit.com/2014/08/12/remote-debugging-issue-with-asp-net-unable-to-attach-to-the-process/

Jack Zhai
  • 6,230
  • 1
  • 12
  • 20