Just FYI: VSCode debugging Issue when using an unconnected target port.

[JMS-1]

We found an quite annoying problem when debugging code using ScpiNet trying to connect to an existing server but using a port which is not LISTENed (connection refused) on - for whatever reason, either mistype or server down.

I am absolutely sure that this is NOT an ScpiNet problem but you might be interested in this issue I posted for VSCode. The reproduction code is based on the (in my opinion totally correct) way you open the TcpClient connection.

microsoft/vscode#249930

[klasyc]

Thank you for the information. I develop the library in Visual Studio, therefore I haven't encountered this issue yet.