Sync .NET cwd, bake version, pass /O absolute #13

2026-05-08T13:35:48-04:00

justin commented

2026-05-08 13:35:48 -04:00

Three changes to isolate/fix the "system cannot find the path specified" failure on the Gitea runner: sync .NET CurrentDirectory alongside Push-Location, bake AppVersion into a temp .gen.iss (no /D), and pass /O so OutputDir doesn`'t depend on cwd. Also dumps the iscc log file and prints PS-vs-.NET cwd before/after.

Three changes to isolate/fix the "system cannot find the path specified" failure on the Gitea runner: sync .NET CurrentDirectory alongside Push-Location, bake AppVersion into a temp .gen.iss (no /D), and pass /O<absolute> so OutputDir doesn`'t depend on cwd. Also dumps the iscc log file and prints PS-vs-.NET cwd before/after.

justin added 1 commit 2026-05-08 13:35:49 -04:00

Sync .NET cwd, bake version into temp .iss, pass /O absolute c86d2363c1

Previous run produced "The system cannot find the path specified."
with exit 2 right after ISCC's banner — ISPP loaded fine (Martijn Laan
copyright printed) but then 200ms of work and silent path failure.
Three changes to isolate/fix:

- Sync `[System.IO.Directory]::SetCurrentDirectory` alongside
  Push-Location. PowerShell's Push-Location updates the PSDrive
  location but not the .NET process cwd that native exes inherit, so
  ISCC may have been resolving `..\dist` against the wrong dir.
- Bake AppVersion into a temp `.gen.iss` instead of passing
  `/DAppVersion=...`, removing /D from the equation.
- Pass `/O<absolute path>` so OutputDir resolution doesn't depend on
  cwd at all.

Also dumps the iscc log file contents and prints PS-vs-.NET cwd before
and after Push-Location so the next run shows whether the divergence
was real.

justin merged commit 1229c52ecf into main

2026-05-08 13:35:50 -04:00

justin deleted branch iscc-cwd-fix

2026-05-08 13:35:50 -04:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: justin/webhook-server#13