Don't show the UI when running CLI commands

[Al12rs]

Improvement

Currently

Running any CLI command will either try to connect to an existing process or create a "main" process to execute the command on. The main process will also start and show the UI (with Startup.Main(services, []);).

We want

To avoid displaying the UI if the CLI command does not require it.
E.g.: uninstall-app command should not start the UI, if there is no application running, should instead execute the "main" process headless.
Some commands on the other hand are supposed to start up the UI (e.g. nxm protocol command).

Supporting Information

The reasons for starting/connecting to a separate process when executing a CLI command are:

• Have a single process handle all commands to have single source of truth and avoid accessing resources separate processes (e.g. applying to the game folder from different processes).
• Be able to close the started CLI process once the CLI command has completed executing. If the user was to start the app while the command was executing, and we didn't have the two steps approach, the CLI process would not be able to exit after completing, since it is now hosting the UI for the user.

The tricky part is that if a "main" headless process was started for a CLI command, and the user then wanted to start the App with ui, we will need a way to start the UI on the existing main headless process.

[MattSturgeon]

Duplicate of #2179 😉

[halgari]

This is possible today by prefixing the command arguments with “as-main”. For example: “as-main protocol-invoke nxm://“

…

On Sat, Dec 14, 2024 at 6:29 PM Matt Sturgeon ***@***.***> wrote: #2179 <#2179> 😉 — Reply to this email directly, view it on GitHub <#2369 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAE72HOTSPGQY5LHD2S443D2FTLOPAVCNFSM6AAAAABTPLUYS6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBTGQYDGMJZGU> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>