Remote SSH Debugging tool for Visual Studio 2022 (ARM/ARM64/Raspberry Pi compatible)
-
SSH based authentification needs to be set up between local and remote. Follow the following guide: https://www.onmsft.com/how-to/how-to-generate-an-ssh-key-in-windows-10
Set the private key on the local machine as
~\.ssh\id_rsa. Set the public key on the remote machine as~/.ssh/authorized_keys. -
Make sure that the remote machine has a user able to run non-shell commands without a password. This is already configured on a RPi.
Make sure the keys are working before proceeding!!
- Install this extension
- In Visual Studio go to
Tools -> Options -> VsRemoteDebugger -> Remote Machine Settingsand modify the access settings - In Visual Studio go to
Tools -> (click on) Start Remote Debugger
- Builds the solution in Visual Studio
- Creates the necessary file structure on the remote machine
- (optional) if running for the first time, installs Visual Studio's vsdbg debugging server on the remote machine
- Copies the files from the output folder into the remote machine
- Connects to the VsDbg server and starts debugging the current project via SSH
Remote debugging only available for ARM-based machines (for now)Now ARM64 compatible- Visual feedback is poor when running for the first time
- Not tested (and most likely not working) for 32-bit versions of Windows
- Command line arguments can be used as long as the project doesn't have more than one debugging profile (check by going to Visual Studio -> Project Settings -> Debugging -> Profile dropdown). If the dropdown has more than one entry, then command line arguments cannot be used.
- Currently not compatible with Open-SSH 8.8 due to underlying library bug.
In a nutshell, if you have a web project (Blazor, ASP .NET) that requires a static assets folder (wwwroot) then enable publishing (Tools -> Settings -> VsRemoteDebugger -> Local Machine Settings -> set publish to true).
Publishing is performed by invoking an external console and executing dotnet publish in the context of the current solution. This had to be done this way due to some inherit problems in Visual Studio's API.
By default the publish flag is set to false, in which case we're programatically triggering a Build using Visual Studio's API. This method is more robust, but does not copy the static assets required for web projects.
