This is a quick follow up to my previous article on Debug Visualizers.
I was having some problems using my new visualizers during a remote debugging session the other day. Every time I tried to use the visualizer I was told the visualizer dll file, or one of it's dependencies could not be loaded. This seemed strange as it had been working earlier in the day.
I realised that 'earlier' I hadn't been in a remote debug session, but rather a local one. I confirmed the visualizer still worked in a local debug session. I decided the problem must be the visualizers weren't installed on the remote PC. I installed them, and tried the debug session again and my problems went away.
It was only at this point I remembered reading that Debug Visualizers work have code that runs on both the debugee and debugger sides, so it does kinda of make sense for the files to be required on both sessions. I guess it's too much work, or too hard for the compiler, for the local Visual Studio to send the debugee Visualizer data to the remote session each time it connects.
In any case, if you're trying to use Visualizers across a remote debug session, ensure the remote PC has the Visualizers installed first.