A bunch of error message updates, library hack, etc.

[magnusjjj]

• Updated all the libraries, and changed the manifest to be able to target newer visual studio.
• Changed SSH.net library to be a static, bundled one. This is nasty. The reason I did this, is that the new default for ssh-keygen on window generates a certificate with changes that makes SSH.net unable to load the certificate, with a very unhelpful error message. See Support OpenSSH 8.8 sshnet/SSH.NET#883
• I moved around some things, and threw exceptions higher, so that you get actual error messages, even if they look ugly, other than 'Connection refused'. It's not the best, but is at the very least very helpful.
• Added in a mkdir -p command, to make sure the target directory actually exists on the remote side
• Changed the static paths to ssh, scp. These are wrong for the bundled windows 10 versions. Now they instead assume that ssh is in %PATH% which is probably better?
• Fixed a problem where if there was an issue with a transfer, it would keep adding the connection event to the build event list, so it would try to connect to the server more and more times.
• Commented out the code that tries to figure out what architecture the remote computer is, in order to install vsdbg. Reason for this is that there was no case for x86, and when I looked at the actual script being downloaded, it supposedly figures out the architecture on its own. Is that correct? It worked well for me, but I don't have a raspberry pi connected.
• Put in a toolbar, with a single button that starts remote debugging.

My plan going forward before I quit is to add the possibility to have multiple configurations, with a simple window. Dropdown to switch between them on the toolbar. Maybe store it as a JSON in the users home directory? :) What do you think?

[radutomy]

• Updated all the libraries, and changed the manifest to be able to target newer visual studio.

Looks good.

• Changed SSH.net library to be a static, bundled one. This is nasty. The reason I did this, is that the new default for ssh-keygen on window generates a certificate with changes that makes SSH.net unable to load the certificate, with a very unhelpful error message. See Support OpenSSH 8.8 sshnet/SSH.NET#883

I'm going to hold off on this for now until the ssh.net team fixes this issue. Will put up a warning message in the meantime.

• I moved around some things, and threw exceptions higher, so that you get actual error messages, even if they look ugly, other than 'Connection refused'. It's not the best, but is at the very least very helpful.

Looks good.

• Added in a mkdir -p command, to make sure the target directory actually exists on the remote side

Looks good.

• Changed the static paths to ssh, scp. These are wrong for the bundled windows 10 versions. Now they instead assume that ssh is in %PATH% which is probably better?

Direct path referencing didn't work for me, something to do with the way scp x64/x86 was invoked. Forgot the exact reason, but I'll do some testing before merging.

• Fixed a problem where if there was an issue with a transfer, it would keep adding the connection event to the build event list, so it would try to connect to the server more and more times.

Good spot!

• Commented out the code that tries to figure out what architecture the remote computer is, in order to install vsdbg. Reason for this is that there was no case for x86, and when I looked at the actual script being downloaded, it supposedly figures out the architecture on its own. Is that correct? It worked well for me, but I don't have a raspberry pi connected.

This needs a bit of testing, but looks good otherwise.

• Put in a toolbar, with a single button that starts remote debugging.

I am not convinced by this as I am a fan of keeping toolbar clutter to a minimum, but people have requested this in the past so lets give it a shot.

• My plan going forward before I quit is to add the possibility to have multiple configurations, with a simple window. Dropdown to switch between them on the toolbar. Maybe store it as a JSON in the users home directory? :) What do you think?

Agreed multiple configs are useful, but any reason for not using existing window in Settings -> Options -> VsRemoteDebugger?

I'll do the merge when I'm on my laptop, shortly after new year.

[radutomy]

Closed. See #16