Fix Windows support: persistent mode, relaunch script, and terminal launch#130
Merged
Fix Windows support: persistent mode, relaunch script, and terminal launch#130
Conversation
PureWeen
force-pushed
the
fix/test-20260217-0552
branch
from
cde5164 to
747194e
Compare
…pt, and terminal launch - Fix GetBundledCliPath/ResolveBundledCliPath to use copilot.exe on Windows - Fix ResolveSystemCliPath to use Path.PathSeparator and Windows npm paths - Add relaunch.ps1 (Windows equivalent of relaunch.sh) - Fix LaunchCopilotInTerminal to use PowerShell on Windows instead of chmod/Terminal.app - Fix BuildCopilotPrompt to use correct target framework on Windows - Fix system message to use relaunch.ps1 on Windows
PureWeen
force-pushed
the
fix/test-20260217-0552
branch
from
747194e to
e0d9085
Compare
PureWeen
added a commit
that referenced
this pull request
Mar 11, 2026
The build command doesn't specify -r win-x64, so dotnet outputs to the non-RID folder (bin\Debug\net10.0-windows10.0.19041.0\) rather than the RID-specific subfolder (win-x64\). This bug was introduced in the original script (PR #130) and caused launch failures on fresh clones where no previous RID-specific build existed. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
PureWeen
added a commit
that referenced
this pull request
Mar 11, 2026
## Problem \ elaunch.ps1\ was looking for the exe in \�in\Debug\net10.0-windows10.0.19041.0\win-x64\ but the build command doesn't specify \-r win-x64\, so dotnet outputs to \�in\Debug\net10.0-windows10.0.19041.0\ (no RID subfolder). This bug was introduced in the original script creation (PR #130) and caused launch failures: \\\ Start-Process: This command cannot be run due to the error: The system cannot find the file specified. \\\ ## Root Cause The script hardcoded \\win-x64\ in \\\ but the build command was: \\\powershell dotnet build PolyPilot.csproj -f net10.0-windows10.0.19041.0 \\\ Without \-r win-x64\, the output goes to the framework folder directly. ## Fix Remove \\win-x64\ from \\\ to match the actual build output location. ## Testing Verified the fix works - build succeeds and app launches correctly. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes several issues preventing PolyPilot from working correctly on Windows.
Persistent Mode Binary Resolution
Relaunch Script
elaunch.ps1\ (Windows equivalent of
elaunch.sh)
elaunch.sh\ to match MauiDevFlow pattern (kill-before-launch to free ports)
Terminal Launch (Fix a Bug / Add a Feature)
elaunch.ps1\ on Windows
MauiDevFlow
All changes are backward-compatible with Mac Catalyst.