Files
PS_Launcher/build-installer.bat
j.foucher ce3979d131 v0.14.0 — rename PSLauncher.exe → PS_Launcher.exe (with backward compat)
Aligns the executable name with the repo / product naming. Backward-
compatible: existing installs that have PSLauncher.exe on disk continue
to work — the self-updater overwrites the file at the running .exe path
without renaming, so the historical filename persists on those machines.

Changes
- AssemblyName : PSLauncher → PS_Launcher (both App and Updater csproj)
- Inno Setup : MyAppExeName, MyUpdaterExeName, OutputBaseFilename all
  now use PS_Launcher prefix
- LauncherSelfUpdater : looks for PS_Launcher.Updater.exe first, falls
  back to legacy PSLauncher.Updater.exe so old installs keep updating
- Build scripts (build-launcher / build-updater / build-installer /
  build-all) : taskkill both legacy AND new names; output paths printed
  with new names
- .gitignore : added PS_Launcher.exe / PS_Launcher.Updater.exe /
  PS_Launcher-*.exe patterns alongside the legacy ones; also ignored
  the WebView2 user-data folder and Office ~$ lock files
- Server admin/launcher.php : URL pattern now generates
  PS_Launcher-{ver}.exe ; SignManifest's existing tolerant glob
  *{ver}*.exe still matches both names
- Versions bumped to 0.14.0 (App + Updater + installer .iss)

Migration story for clients
- Brand-new install via PS_Launcher-Setup-0.14.0.exe → PS_Launcher.exe
  on disk
- Existing install (PSLauncher.exe) auto-updates to v0.14 → file stays
  named PSLauncher.exe but contains v0.14 code; self-updater fallback
  ensures future updates keep working

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-03 09:55:41 +02:00

34 lines
1.1 KiB
Batchfile

@echo off
REM Wrapper pour lancer la creation de l'installeur Inno Setup.
REM Pre-requis :
REM - .NET 8 SDK
REM - Inno Setup 6 (installe par defaut dans C:\Program Files (x86)\Inno Setup 6)
REM
REM Usage : double-clic sur ce fichier, ou en cmd : build-installer.bat
REM
REM Si Inno Setup est installe ailleurs, lance directement le .ps1 :
REM powershell -ExecutionPolicy Bypass -File installer\build-installer.ps1 -ISCC "C:\Chemin\ISCC.exe"
setlocal
set "SCRIPT_DIR=%~dp0"
REM Termine les eventuelles instances en cours qui verrouilleraient les .exe
REM (les deux noms : legacy PSLauncher et nouveau PS_Launcher >= v0.14.0)
taskkill /F /IM PSLauncher.exe /T >nul 2>&1
taskkill /F /IM PSLauncher.Updater.exe /T >nul 2>&1
taskkill /F /IM PS_Launcher.exe /T >nul 2>&1
taskkill /F /IM PS_Launcher.Updater.exe /T >nul 2>&1
powershell -NoProfile -ExecutionPolicy Bypass -File "%SCRIPT_DIR%installer\build-installer.ps1" %*
set "EXITCODE=%ERRORLEVEL%"
echo.
if %EXITCODE% NEQ 0 (
echo [ECHEC] Le build de l'installeur a echoue avec le code %EXITCODE%.
) else (
echo [OK] Installeur genere avec succes.
)
echo.
pause
endlocal & exit /b %EXITCODE%