AGENT SKILL

bt-build

Fast incremental C++/MSBuild builds using bt. Use when the user wants to compile, build, check what's dirty, or query build dependencies in a repo that has .vcxproj files. Prefer bt over invoking MSBuild directly for inner-loop source changes (.cpp, .h, .idl, .xaml, .appxmanifest).

License 许可
MIT
最近更新
2026-11-14
Stars
★ 8.6k
Forks
965

01 前言 Front Matter

name
bt-build
description
Fast incremental C++/MSBuild builds using bt. Use when the user wants to compile, build, check what's dirty, or query build dependencies in a repo that has .vcxproj files. Prefer bt over invoking MSBuild directly for inner-loop source changes (.cpp, .h, .idl, .xaml, .appxmanifest).
allowed-tools
shell

02 资源文件 1

03 SKILL.md 正文

bt — Fast Inner-Loop Builds

bt reads an MSBuild binary log and replays only the dirty compile/link/MIDL/XAML/makepri steps directly — no MSBuild overhead.

Use bt for the edit-build-debug cycle on source files only. For anything else, use the build skill (MSBuild).

Headers not yet in the tlog (newly added #includes) bt won't trigger rebuilds until the next msbuild -bl.

Do NOT use bt when

Any of these are true → use the build skill (MSBuild) instead:

  • .vcxproj or .vcxitems files were added, removed, or edited
  • .props or .targets files were changed
  • NuGet package dependencies changed
  • WinRT runtime classes were added or removed
  • Packaging, signing, or AppX bundling is needed
  • First build of the repo (no binlog exists yet)
  • You are unsure whether bt covers the change

When in doubt, use MSBuild.

Before you start

1. Check if bt is installed

Run bt --version. If bt is missing, run the install-bt.ps1 script from this skill's directory to download and install it. Periodically run it to update bt as well.

2. Pick the right binlog

bt needs a binlog from a prior MSBuild build. The repo's build scripts all write to BuildOutput\ with names like:

Binlog Scope
Microsoft.UI.Xaml.<flavor>.binlog full product (incl. Controls DLL) — prefer for product code
MUXControls.<flavor>.binlog test apps + infra — prefer for test code
Microsoft.ui.xaml.<flavor>.binlog Microsoft.UI.Xaml.dll only — NOT Controls (mux subset)
Microsoft.UI.Xaml-Product.<flavor>.binlog full product (alternate) — fallback for product code
Microsoft.UI.Xaml.Controls.<flavor>.binlog Controls DLL only — narrow fallback
XamlCompilerPrerequisites.<flavor>.binlog compiler tools — not used by bt

<flavor> is amd64chk, arm64fre, etc. Single-project builds via msb/build-clang produce <project>.<flavor>.binlog next to these.

To pick:

  1. Classify the change by edited paths — test (table below) / mux (dxaml/xcp/ only) / product (everything else under controls/dev, controls/idl, dxaml/, src/).
  2. Pick the freshest binlog whose scope covers that classification, preferring broader scopes (product covers Controls, etc.).
  3. Infer <flavor> from the chosen filename.
  4. Pass --binlog BuildOutput\<chosen> to every bt invocation. bt has no useful default to fall back to.

Caveats:

  • On NTFS, Microsoft.UI.Xaml.<flavor>.binlog and Microsoft.ui.xaml.<flavor>.binlog collide — content is whoever wrote last; trust mtime + size, not casing.
  • If product and test binlogs exist with mtimes >1h apart, warn that the set may be inconsistent.
  • If no binlog exists, run the build skill.

Test path classification

Anything under these directories is test scope:

  • controls/test/MUXControls.Test/
  • controls/test/MUXControlsTestApp/
  • controls/test/TabViewTearOutApp/
  • controls/test/TestAppCX/
  • controls/test/IXMPTestApp/
  • controls/test/MUXTestInfra/ (if present)
  • Samples/AppTestAutomationHelpers/

Common workflows

Command What it does
bt build Build everything dirty (always pass --binlog BuildOutput\<x>.binlog)
bt build MyFile.cpp Forward walk: compile + relink anything affected by this source
bt build MyApp.dll Backward walk: only what this target needs
bt build -c [target] Compile only — skip link/lib
bt build -n Dry run — print commands without executing
bt watch [--run <cmd>] Build on file change; optionally run a command after
bt [--binlog some.binlog] dirty [target] What needs building now?
bt bins MyHeader.h What rebuilds when this header changes?
bt srcs [--headers] MyApp.dll Sources (and optionally #included headers) feeding this target

Run bt --help for command options (--binlog <path>), bt <subcommand> --help for subcommand options like -j <N>, --debounce <ms>, etc.

04 同仓库更多 Skills

microsoft
microsoft/microsoft-ui-xaml

analyze-session

Opens a WinUI Profiler session file (.sqlite) and answers questions about a WinUI 3 app's performance from it with the winui-profiler tools: how the launch went, UI-thread ticks and slow ticks, regions of interest (navigations, flyouts and dialogs opening, focus changes), and the UI elements and composition visuals the events mention. Use it when someone asks why a WinUI app is slow to start or draws slowly, what a tick did, what happened around a navigation or to an element, or what a session holds, and for /winui-profiler:analyze-session [session.sqlite | folder].

★ 8.6k
microsoft
microsoft/microsoft-ui-xaml

test-suite-setup

Complete end-to-end setup and execution of the WinUI3 test suite locally. Delegates building to the build skill, then handles test payload creation, machine setup, and running all tests.

测试与质量Skill与智能体开发
★ 8.6k
microsoft
microsoft/microsoft-ui-xaml

test-on-vm

EXPERIMENTAL. Run locally built WinUI interaction tests on a Hyper-V VM through PowerShell Direct. Use when asked to run WinUI tests on a local VM.

测试与质量
★ 8.6k
microsoft
microsoft/microsoft-ui-xaml

code-review

Review changes in microsoft/microsoft-ui-xaml. Use when reviewing code or pull requests in this repository.

开发工程师代码审查
★ 8.6k
microsoft
microsoft/microsoft-ui-xaml

code-coverage-calculation

EXPERIMENTAL. Calculate code coverage of a WinUI control or component (for example "calculate coverage of control TitleBar") by running only that component's tests on a local Hyper-V VM against the local build. Supports controls in Microsoft.UI.Xaml.Controls.dll and Microsoft.UI.Xaml.Controls.Tabular.dll, and dxaml types in Microsoft.ui.xaml.dll. Reports per-file and per-function line coverage that matches the ADO Code Coverage tab. Use for "calculate/measure/get coverage of <control>", "how much do <control>'s tests cover", or "coverage before/after my tests" when you have a local build and a VM.

开发工程师Skill与智能体开发
★ 8.6k