Fix build issue for wslsettings, and add more logging to the pipelines

[Flor Chacón (florelis)]

Summary of the Pull Request

Fixes the recurring build error

CSC : error CS0016: Could not write to output file 'C:\__w\1\s\src\windows\wslsettings\obj\x64\Release\generated\WinRT.SourceGenerator\Generator.WinRTAotSourceGenerator\WslSettings.Views.Settings.AboutPage.WinRTVtable.g.cs' -- 'Could not find a part of the path 'C:\__w\1\s\src\windows\wslsettings\obj\x64\Release\generated\WinRT.SourceGenerator\Generator.WinRTAotSourceGenerator\WslSettings.Views.Settings.AboutPage.WinRTVtable.g.cs'.' [C:\__w\1\s\src\windows\wslsettings\wslsettings.csproj]

PR Checklist

• Closes: Link to issue #xxx
• Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
• Tests: Added/updated if needed and all pass
• Localization: All end user facing strings can be localized
• Dev docs: Added/updated if needed
• Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments

The build often fails when attempting to write auto-generated source files related to WinUI in wslsettings. The failure seems to happen because the directory for those files does not exist when trying to create the file. These generated files are usually compiled in memory, but on official builds CodeQL forces them to be written to disk for analysis by setting the MSBuild property EmitCompilerGeneratedFiles=true. MSBuild usually ensures that the directory exists with the CreateCompilerGeneratedFilesOutputPath target which is configured to run before the CoreCompile target. However, the WinUI auto-generated files are created in the XamlPreCompile target, which does not have a dependency on CreateCompilerGeneratedFilesOutputPath, so it is not guaranteed to run after it.

The fix for the build failure is to add a target that ensures the directory exists before XamlPreCompile runs.

This PR also sets MSBuild to output binlogs to the pipeline artifacts to make it easier to debug pipeline failures in the future.

Validation Steps Performed

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

[Blue (OneBlue)]

LGTM. Validated that the release pipeline produces binlogs for all iterations

[Copilot]

🔵 Needs a closer look

The pipeline binlog path can fail if $(ob_outputDirectory)\binlogs doesn’t exist yet, which can break builds until the directory is created before invoking MSBuild with /bl:.

Review details

Suppressed comments (1)

.pipelines/build-job.yml:133

• MSBuild /bl: fails if the parent directory doesn’t exist; currently nothing creates $(ob_outputDirectory)\binlogs (or even $(ob_outputDirectory)) before the first cmake --build call, so builds can fail when binlogging is enabled. Create the binlogs directory before invoking any cmake --build commands (and quote the /bl: path).

          - script: cmake --build . --config Release --target ${{ target.target }} -- -m /bl:$(ob_outputDirectory)\binlogs\${{ parameters.platform }}-${{ replace(target.target, ';', '-') }}.binlog

• Files reviewed: 2/2 changed files
• Comments generated: 0 new
• Review effort level: Lite

[ranm-msft]

Verified the binlog paths come out target-specific now, so the per-target runs don't clobber each other, and the wrapper target pulls in CreateCompilerGeneratedFilesOutputPath rather than hand-rolling the MakeDir. Both look right to me.

LGTM.