Skip to content

Fix the winforms build output path in the manifest - #119

Merged
AmirMS (AmelBawa-msft) merged 1 commit into
microsoft:mainfrom
26zl:pr/manifest-winforms-bin
Sep 29, 2026
Merged

AmirMS (AmelBawa-msft) merged 1 commit into
microsoft:mainfrom
26zl:pr/manifest-winforms-bin

Conversation

@26zl

Copy link
Copy Markdown
Contributor

I ran the CI harness locally to check my own changes, which is how I noticed that the winforms flow cannot pass as written.

src/manifest.yml builds the WinForms hello world with -o tests/winforms/bin but runs src\tests\winforms\bin\hello.exe, so the run step never finds the binary. The flow is manual_test: true, which is presumably why CI has not caught it.

Both paths now use src/tests/winforms/bin, matching the dotnet and winui flows.

Checked on Windows 11 Pro 25H2 (build 26200.9550) with dotnet 10.0.401, running the manifest's build, run and expected values through ./src/tests/_harness/run-flow.ps1 -Id winforms from the repository root on 06200f0. With the current manifest, dotnet build succeeds and writes tests/winforms/bin/hello.exe, then the run step fails with The system cannot find the path specified. (run failed with exit code 1). With this change the same run prints WinForms: hello-winforms and FLOW_OK: winforms.

Thanks for having a look.

The build wrote hello.exe to tests/winforms/bin while the run step
executed src\tests\winforms\bin\hello.exe, so the manual flow could not
pass as written. Both now use src/tests/winforms/bin, matching the
dotnet and winui flows.
@AmelBawa-msft
AmirMS (AmelBawa-msft) merged commit 2f93c4e into microsoft:main Sep 29, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants