SuessLabs / VsLinuxDebug

VS Extension to remotely deploy and debug your .NET (Core) C# solutions directly to your Linux or Raspberry Pi devices! .NET Core 3.1, .NET 5, 6, 7, 8, 9
https://marketplace.visualstudio.com/items?itemName=SuessLabs.VSLinuxDebugger
MIT License
38 stars 9 forks source link

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

Closed jorgedevs closed 1 year ago

jorgedevs commented 1 year ago

Not sure how else I could reach out to post a question but when I try both Build and Deploy, and Build, Deploy and Debug, am I expecting that the app will run automatically on my target linux machine? because it doesnt, I have to go to where the project was uploaded and do dotnet run to run it.

Would be cool if it runs by itself like I would run a Windows app, Android app on a phone, etc.

Thanks in advance, this tool is still super helpful to me. Nice work!

DamianSuess commented 1 year ago

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 commented 1 year ago

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 commented 1 year ago

@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.

Build-Deploy-Execute

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