-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should "Build and Deploy" start the app automatically on my Linux target machine? #72
Comments
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 |
Sure, I'm working on an Avalonia 11 application and my setup is: Dev Machine: Target machine: 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 |
@jorgedevs, 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. 👍 |
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!
The text was updated successfully, but these errors were encountered: