Cosmos.VS.Windows message handling needs improvement

[mterwoord]

The DebugConnector and the Cosmos.VS.WIndows project communicate via named pipe. messages received in the .Windows project are put in a queue, and a timer is used to process them (marshalling back to the UI-thread) It looks like the current way things work keep the UI-thread too busy for rendering. (VS will freeze up) Replacing UI-interaction with a streamwriter (still on ui thread) works and makes cpu usage go down..

[Geramy]

Also the debugger needs to detect that the pipe is still open but the Virtual Machine software has crashed. So that you dont have to close all visual studio windows to debug on a VM again, PIPE Busy error.

[selkij]

Can be closed

[GoldenretriverYT]

Why? I am still getting busy pipes errors, even when just normally exiting VMWare