Skip to content

Latest commit

 

History

History
34 lines (20 loc) · 2.61 KB

File metadata and controls

34 lines (20 loc) · 2.61 KB

Agent Guidance

Build environment

Visual Studio 2026 is installed and builds this solution successfully. Treat the VS 2026 IDE or its associated developer-command environment as the authoritative local build environment for this repository.

Do not infer that C++ builds are unavailable merely because a separate Build Tools installation lacks Visual C++ targets. When a build is needed, use the installed Visual Studio 2026 environment and report the exact configuration and result.

GitHub Actions runner

The GitHub Actions runner is a self-hosted machine that runs without administrator rights by default. Workflows must not assume they can install into protected locations or perform privileged system configuration; required SDKs and tools must be pre-provisioned or checked explicitly.

Testing parity and regression checks

The GitHub Actions pipelines and scripts/runtests.ps1 must reproduce the same testing conditions and follow the same testing process. Keep both in parity, including toolchain and build configuration, prerequisites, environment settings, test inputs and filters, check ordering, and failure and skip policies. When either testing path changes, update the other as needed to preserve parity.

Before declaring source-code or build/test configuration changes complete, execute scripts/runtests.ps1 under the corresponding pipeline conditions to check for regressions. A successful build or a subset of checks does not replace this required run. Report the invocation and result, including any failures, skips, or unavailable prerequisites; do not claim regression validation is complete if the required run could not finish.

Source-change documentation

Every source-code change must include a concise nearby comment that documents the change's intent. Keep the comment focused on the reason for the change, invariant, or compatibility constraint it preserves rather than restating the code.

Suggested local commands

The following paths and command are examples verified on one development machine only. They are suggested starting points, not portable requirements: they may be absent or different on another filesystem or computer.

$vsDevCmd = 'C:\Program Files\Microsoft Visual Studio\18\Insiders\Common7\Tools\VsDevCmd.bat'
$project = 'C:\Projects\FileManager\src\vcxproj\salamand.vcxproj'
$cmd = 'call "' + $vsDevCmd + '" -arch=x64 -host_arch=x64 && msbuild "' + $project + '" /t:Build /p:Configuration=Debug /p:Platform=x64 /m'
& $env:ComSpec /d /s /c $cmd

This uses the Visual Studio developer environment before invoking MSBuild, rather than relying on a standalone Build Tools installation.