Should "Build and Deploy" start the app automatically on my Linux target machine?

[jorgedevs]

Should "Build and Deploy" start the app automatically on my Linux target machine?

[DamianSuess]

Thank you, @jorgedevs, for reaching out. This feature is still in the testing phase as I've found it doesn't always work from environment-to-environment. Looking to improve the system to make it better.

What environment are you deploying to? (Linux Distro, version, .NET version, and is it GUI or CLI)

In the meantime, are you able to manually attach to the debugger via Visual Studio after deploying it?

https://github.com/SuessLabs/VsLinuxDebug/wiki/Debugging-Manually

See also, #49 Launch GUI after Deploying Package

[jorgedevs]

Sure, I'm working on an Avalonia 11 application and my setup is:

Dev Machine:
Windows 11 (Latest stable version)
Visual Studio 2022 (17.7.4)
.NET 7.0.401

Target machine:
SeeedStudio reTerminal
Linux Debian (11)
.NET 7.0.305
GUI

I am able to attach the debugger, but dont need it at the moment, so I just use your extension to build and transfer the project to the target device, then I vnc in to run dotnet <myapp>,dll to run it.

[DamianSuess]

@jorgedevs,
By the way, to directly answer the issue's title question, "Build and Deploy" only builds the application and then deploys it to the target machine. The feature you're ideally referring to is, "Build, Deploy, and Launch (experimental)" which is still getting the kinks worked out.

At the moment, this feature (#49) is temperamental due to individual environments. Getting feedback from members like yourself really helps. I was able to kick off the GUI from SSH manually, but not with SSH.NET.

In the meantime, I hope you keep having success with this extension and it helps speed up your deployments for testing. 👍