j.foucher
ce3979d131
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>
39 lines
1.1 KiB
Batchfile
39 lines
1.1 KiB
Batchfile
@echo off
|
|
REM Build complet : launcher + updater (sans creer l'installeur).
|
|
REM Pour l'installeur Inno Setup, utiliser build-installer.bat.
|
|
|
|
setlocal
|
|
set "REPO=%~dp0"
|
|
echo.
|
|
echo ==^> Termine les eventuelles instances qui verrouilleraient les .exe
|
|
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
|
|
echo.
|
|
echo ==^> dotnet publish PSLauncher.App (Release single-file)
|
|
echo.
|
|
dotnet publish "%REPO%src\PSLauncher.App\PSLauncher.App.csproj" -c Release --nologo
|
|
if %ERRORLEVEL% NEQ 0 goto :fail
|
|
|
|
echo.
|
|
echo ==^> dotnet publish PSLauncher.Updater (Release single-file)
|
|
echo.
|
|
dotnet publish "%REPO%src\PSLauncher.Updater\PSLauncher.Updater.csproj" -c Release --nologo
|
|
if %ERRORLEVEL% NEQ 0 goto :fail
|
|
|
|
echo.
|
|
echo [OK] Les deux exes sont disponibles a la racine du repo :
|
|
echo %REPO%PS_Launcher.exe
|
|
echo %REPO%PS_Launcher.Updater.exe
|
|
echo.
|
|
pause
|
|
endlocal & exit /b 0
|
|
|
|
:fail
|
|
echo.
|
|
echo [ECHEC] Build echoue avec le code %ERRORLEVEL%.
|
|
echo.
|
|
pause
|
|
endlocal & exit /b %ERRORLEVEL%
|