aboutsummaryrefslogtreecommitdiffstats
path: root/packages/meshbay-client/build/appx-extensions.xml
diff options
context:
space:
mode:
Diffstat (limited to 'packages/meshbay-client/build/appx-extensions.xml')
-rw-r--r--packages/meshbay-client/build/appx-extensions.xml16
1 files changed, 14 insertions, 2 deletions
diff --git a/packages/meshbay-client/build/appx-extensions.xml b/packages/meshbay-client/build/appx-extensions.xml
index 1ee1cca..3326dd8 100644
--- a/packages/meshbay-client/build/appx-extensions.xml
+++ b/packages/meshbay-client/build/appx-extensions.xml
@@ -1,3 +1,15 @@
- <desktop:Extension Category="windows.startupTask" Executable="app\resources\node-runtime\meshbay-node.exe" EntryPoint="Windows.FullTrustApplication">
- <desktop:StartupTask TaskId="MeshBayNodeStartup" Enabled="true" DisplayName="MeshBay Node" />
+ <!-- At sign-in: off until the user picks that mode on the Node page, which
+ switches it through `meshbay-node autostart`. meshbay-nodew.exe, the build
+ without a console: Windows runs a startup task's executable as is, and
+ the console one opened a window whose close button stopped the node. -->
+ <desktop:Extension Category="windows.startupTask" Executable="app\resources\node-runtime\meshbay-nodew.exe" EntryPoint="Windows.FullTrustApplication">
+ <desktop:StartupTask TaskId="MeshBayNodeStartup" Enabled="false" DisplayName="MeshBay Node" />
</desktop:Extension>
+ <!-- `meshbay-node` in a terminal: %LOCALAPPDATA%\Microsoft\WindowsApps is
+ on PATH already and this alias keeps its path across versions, where a
+ PATH entry naming the install folder went stale at each update. -->
+ <uap5:Extension Category="windows.appExecutionAlias" Executable="app\resources\node-runtime\meshbay-node.exe" EntryPoint="Windows.FullTrustApplication">
+ <uap5:AppExecutionAlias>
+ <uap5:ExecutionAlias Alias="meshbay-node.exe" />
+ </uap5:AppExecutionAlias>
+ </uap5:Extension>