Files
TeslaSuite/Console/RedPlanet/Apps.xml
T
CydandClaude Opus 4.8 4c15197b34 Console/launcher-managed RIOJoy + real product uninstall
RIOJoy lifecycle is now owned by the console + launcher (the auto-start Run entry
was removed on the RioJoy side): Apps.xml autoRestart false -> true, so the
launcher starts RIOJoy and keeps it alive. Safe with uninstall — the watcher only
relaunches a still-tracked process, and uninstall's kill untracks it first.

Uninstall now physically removes the product (was unregister-only):
- Agent CmdUninstallApp: after kill + unregister, reports the product's
  C:\Games\<dir> to clean up — but only if no remaining registered launch entry
  still uses that folder (orphan check keeps multi-entry products like Red Planet's
  GameClient/LC/MR intact until the last entry is removed).
- Service (SYSTEM): on UninstallApp, runs <dir>\pre-uninstall.bat if present
  (RIOJoy's removes ViGEmBus + config) then deletes the directory, on a background
  thread so it can't trip the Console's RPC timeout. Path-guarded to only ever
  delete a proper subdirectory of C:\Games. Logged to podconf.log.

74 tests green; the cleanup path is pod-behavior, not unit-tested here.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-30 18:53:09 -05:00

100 lines
4.3 KiB
XML

<?xml version="1.0" encoding="utf-8"?>
<!--
Tesla Console product catalog.
This file is the single source of truth for installable products and the
launch entries each one registers on a pod. It replaces the products that
were previously hardcoded in SiteManagement.cs.
Element/attribute reference:
<Product id = install/product key (Guid) used while transferring the package
name = friendly product name (used in menu + status text)
menuText = exact text shown in the Install Product submenu
hostTypeDialog = "true" to prompt for resolution + roles
(Game Client / Live Camera / Mission Review),
"false" to register all launch entries as-is>
<Launch key = launch entry Guid registered on the pod (LaunchData.LaunchKey)
displayName = name shown in the pod's app list
exe = absolute path to the executable on the pod
args = command-line arguments; "{res}" expands to " -res W H"
when a custom resolution was chosen, otherwise to ""
workingDirectory = optional; defaults to the directory of exe
autoRestart = "true"/"false"
hostType = GameClient | LiveCamera | MissionReview | None
(only meaningful when hostTypeDialog="true"; an entry
is registered only if its role was selected) />
</Product>
To add a product, append a <Product> with one <Launch>. exe must live under
the install directory the package extracts to (currently C:\Games\...).
-->
<AppCatalog>
<Product id="7D241B1F-AB6D-4e08-9C20-12294E743D94"
name="Red Planet 4.11"
menuText="Red Planet 4.11..."
hostTypeDialog="true">
<Launch key="7D241B1F-AB6D-4e08-9C20-12294E743D94"
displayName="Red Planet 4.11"
exe="C:\Games\RP411\rpl4opt.exe"
args="-net 1501{res}"
autoRestart="true"
hostType="GameClient" />
<Launch key="57A0B3C2-D5CF-46d6-ABED-A8F4A26AB086"
displayName="Red Planet 4.11 LC"
exe="C:\Games\RP411\rpl4opt.exe"
args="-net 1501{res} -lc"
autoRestart="true"
hostType="LiveCamera" />
<Launch key="8F71D5C2-38E4-413c-8E22-88CAD08774D2"
displayName="Red Planet 4.11 MR"
exe="C:\Games\RP411\rpl4opt.exe"
args="-net 1501{res} -mr"
autoRestart="true"
hostType="MissionReview" />
</Product>
<Product id="CC8500ED-A653-45a7-BEF8-C332D30371A6"
name="BattleTech Firestorm"
menuText="BattleTech Firestorm..."
hostTypeDialog="false">
<Launch key="CC8500ED-A653-45a7-BEF8-C332D30371A6"
displayName="BattleTech Firestorm"
exe="C:\Games\MW4\launcher.exe"
args=""
autoRestart="true"
hostType="None" />
</Product>
<Product id="8EE93A6C-F16A-49be-B867-37FAE9087FFF"
name="BattleTech Firestorm LC"
menuText="BattleTech Firestorm LC..."
hostTypeDialog="false">
<Launch key="8EE93A6C-F16A-49be-B867-37FAE9087FFF"
displayName="BattleTech Firestorm LC"
exe="C:\Games\MW4\launcher.exe"
args=""
autoRestart="true"
hostType="None" />
</Product>
<!-- RIOJoy — virtual-gamepad feeder for the cockpit RIO board (separate repo,
net48 framework-dependent). Its dist\RIOJoy-<ver>.zip is purpose-built for
Install Product: extracts to C:\Games (giving postinstall.bat + RIOJoy\),
and the launcher runs postinstall.bat as SYSTEM to install the ViGEmBus
driver. The console + launcher then own RIOJoy's lifecycle: the launch entry
below starts it and autoRestart keeps it alive (no logon auto-start entry).
On uninstall the launcher runs RIOJoy\pre-uninstall.bat (removes ViGEmBus +
config) and deletes C:\Games\RIOJoy. -->
<Product id="87FBC2E6-6359-4EF4-96A5-DF157823CFF6"
name="RIOJoy"
menuText="RIOJoy..."
hostTypeDialog="false">
<Launch key="FE83E212-45DF-48F9-848E-0B3CEE0692A3"
displayName="RIOJoy"
exe="C:\Games\RIOJoy\app\RioJoy.Tray.exe"
args=""
autoRestart="true"
hostType="None" />
</Product>
</AppCatalog>