blob: db6e345ff77a44dccd6206b4d313b8f9c6b5d806 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
|
<!-- 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>
<!-- `meshbay-cli` in a terminal, the command-line client: the same alias
mechanism, for the same reason. -->
<uap5:Extension Category="windows.appExecutionAlias" Executable="app\resources\node-runtime\meshbay-cli.exe" EntryPoint="Windows.FullTrustApplication">
<uap5:AppExecutionAlias>
<uap5:ExecutionAlias Alias="meshbay-cli.exe" />
</uap5:AppExecutionAlias>
</uap5:Extension>
|