C
ColinParks
Guest
I am developing a simple Hello World UI using Avalonia (WPF and XAML based) and .Net Core. The purpose is to deploy the app to both Windows and Linux OS.
I've used both Self-Contained and Framework Dependent deployment using .Net Core 2.2 framework. The problem occurs when I deploy it for Windows runtime. When the executable is run, command prompt is opened to run it, which is fine. The problem is that the command prompt stays open and must remain open for the application to stay running (UI to stay up).
It isn't ideal for the user of the application to have the command prompt open at all times if they want to run the app. Is there any way to allow the executable to be run without command prompt opening?
If there is any additional information I need to provide please let me know.
Continue reading...
I've used both Self-Contained and Framework Dependent deployment using .Net Core 2.2 framework. The problem occurs when I deploy it for Windows runtime. When the executable is run, command prompt is opened to run it, which is fine. The problem is that the command prompt stays open and must remain open for the application to stay running (UI to stay up).
It isn't ideal for the user of the application to have the command prompt open at all times if they want to run the app. Is there any way to allow the executable to be run without command prompt opening?
If there is any additional information I need to provide please let me know.
Continue reading...