[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-dotnet-flow-tracing":3,"mdc--sqtpuq-key":27,"related-repo-dotnet-flow-tracing":723,"related-org-dotnet-flow-tracing":818},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":16,"repoUrl":17,"updatedAt":18,"license":19,"forks":20,"topics":21,"repo":22,"sourceUrl":25,"mdContent":26},"flow-tracing","trace .NET dependency flow in VMR","Trace dependency flow across .NET repos through the VMR pipeline. USE FOR: checking if a PR\u002Fcommit from repo A has reached repo B, finding what runtime SHA is in an SDK build, tracing dependency versions through the VMR, checking if a commit is included in an SDK build, decoding SDK version strings, \"has my fix reached runtime\", \"did roslyn#80873 flow to runtime\", \"what SHA is in SDK version X\", cross-repo dependency tracing, mapping SDK versions to VMR commits. DO NOT USE FOR: codeflow PR health or staleness (use flow-analysis skill), CI build failures (use ci-analysis skill). INVOKES: maestro and GitHub MCP tools, Get-SdkVersionTrace.ps1 script.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"dotnet",".NET (Microsoft)","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fdotnet.png",[12],{"name":13,"slug":14,"type":15},"Data Pipeline","data-pipeline","tag",12,"https:\u002F\u002Fgithub.com\u002Fdotnet\u002Farcade-skills","2026-07-12T08:21:55.689056",null,18,[],{"repoUrl":17,"stars":16,"forks":20,"topics":23,"description":24},[],"Reuseable AI skills, plugins, agents for use in the dotnet product repos, such as dotnet\u002Fruntime","https:\u002F\u002Fgithub.com\u002Fdotnet\u002Farcade-skills\u002Ftree\u002FHEAD\u002Fplugins\u002Fdotnet-dnceng\u002Fskills\u002Fflow-tracing","---\nname: flow-tracing\ndescription: >\n  Trace dependency flow across .NET repos through the VMR pipeline.\n  USE FOR: checking if a PR\u002Fcommit from repo A has reached repo B,\n  finding what runtime SHA is in an SDK build, tracing dependency\n  versions through the VMR, checking if a commit is included in an\n  SDK build, decoding SDK version strings, \"has my fix reached runtime\",\n  \"did roslyn#80873 flow to runtime\", \"what SHA is in SDK version X\",\n  cross-repo dependency tracing, mapping SDK versions to VMR commits.\n  DO NOT USE FOR: codeflow PR health or staleness (use flow-analysis\n  skill), CI build failures (use ci-analysis skill).\n  INVOKES: maestro and GitHub MCP tools, Get-SdkVersionTrace.ps1 script.\nallowed-tools: shell\n---\n\n# Flow Tracing\n\nTrace dependency flow across .NET repositories through the VMR pipeline. Two workflows:\n\n1. **Cross-repo flow trace**: Has a change from repo A reached repo B? → Use Steps 1-4 below (reads GitHub files + maestro MCP directly)\n2. **SDK version trace**: What component SHA is in a specific SDK version? → **Run `Get-SdkVersionTrace.ps1`** (handles version decoding, build lookup, and servicing topology automatically)\n\n## Cross-Repo Flow Trace\n\n**Question**: \"Has change X from repo A reached repo B?\"\n\n### Step 1: Resolve the Source Change\n\nIdentify the merge commit SHA in repo A from the PR number, issue number, commit SHA, or description the user provides. If the PR isn't merged yet, stop — the change hasn't entered the pipeline.\n\n### Step 2: Check VMR Intake (source-manifest.json)\n> ⚠️ **Internal branches** (`internal\u002Frelease\u002F*`) exist only on AzDO, not GitHub. Use the AzDO REST API to read files. See [references\u002Finternal-vmr.md](references\u002Finternal-vmr.md).\n\nRead `src\u002Fsource-manifest.json` from `dotnet\u002Fdotnet` on the target VMR branch (usually `main` or `release\u002F*`). This file is the authoritative record of what the VMR has actually consumed — subscription status reflects Maestro's bookkeeping, but the manifest reflects reality. Find the entry for repo A — the `commitSha` field shows the latest commit the VMR has consumed.\n\n**Determine if the change is included** (try in order):\n1. **Date comparison** (fastest): If the VMR commit date is months after the PR merge date, it's included.\n2. **Compare API**: Use GitHub compare endpoint if dates are close.\n3. **Commit history walk**: List recent commits if compare is unavailable.\n\nIf repo A's SHA in source-manifest is not past the merge commit → the change hasn't reached the VMR yet. Check for an open forward flow PR from repo A into `dotnet\u002Fdotnet`.\n\n> ⚠️ **2xx\u002F3xx bands**: Only the **1xx branch** source-builds all components. If tracing to a 2xx\u002F3xx branch, runtime\u002Faspnetcore won't appear in source-manifest — they're consumed as prebuilts from 1xx. See [references\u002Fservicing-topology.md](references\u002Fservicing-topology.md).\n\n### Step 3: Check Downstream Delivery (repo B)\n\nIf the VMR has the change, check if it has flowed to repo B:\n\n> ⚠️ **`eng\u002FVersion.Details.xml`** is the file you want — it contains source dependency entries with `Sha` fields. Do NOT use `eng\u002FVersions.props` (that has NuGet package versions, not source SHAs).\n\n1. **Check subscription health** for repo B using maestro MCP.\n2. **If current**: The change has reached repo B. Confirm by reading `eng\u002FVersion.Details.xml` in repo B.\n3. **If stale**: Read `eng\u002FVersion.Details.xml` in repo B — the `dotnet\u002Fdotnet` entry's `Sha` is the VMR commit repo B last consumed. Check `src\u002Fsource-manifest.json` at *that SHA* for repo A's commitSha. If it's past the merge commit, the change reached repo B despite the stale subscription.\n4. **If stale AND change not in consumed VMR SHA**: Change is in the VMR but hasn't flowed to repo B. Suggest flow-analysis skill for diagnosis.\n\n### Step 4: Report\n\nSummarize the trace chain:\n- \"✅ roslyn#80873 merged at `abc123` → VMR consumed it → runtime backflow current\"\n- \"⚠️ Change in VMR → but runtime backflow is 3 builds behind\"\n- \"❌ PR hasn't merged yet — not in pipeline\"\n\n## SDK Version Trace\n\nRun the script to trace from an SDK version string to a component commit SHA:\n\n```powershell\n# Trace runtime SHA in a specific SDK version\n.\u002Fscripts\u002FGet-SdkVersionTrace.ps1 -SdkVersion \"10.0.300-preview.26117.103\"\n\n# Trace a specific component\n.\u002Fscripts\u002FGet-SdkVersionTrace.ps1 -SdkVersion \"10.0.300-preview.26117.103\" -Component \"aspnetcore\"\n\n# Check if specific commits are included\n.\u002Fscripts\u002FGet-SdkVersionTrace.ps1 -SdkVersion \"10.0.300-preview.26117.103\" -CheckCommit \"b226ba1f77a4\",\"f3bc0212e637\"\n\n# Just decode the version string\n.\u002Fscripts\u002FGet-SdkVersionTrace.ps1 -SdkVersion \"10.0.300-preview.26117.103\" -DecodeOnly\n```\n\nThe script decodes the SDK version, maps to a VMR branch, finds the build in AzDO, and walks the dependency chain through `source-manifest.json` (and `Version.Details.xml` for servicing branches that don't source-build all components).\n\n> ⚠️ **SDK version dates use Arcade's SHORT_DATE formula**: `YY*1000 + MM*50 + DD` (NOT YYDDD day-of-year). `26117` = Feb 17, 2026, NOT April 27. See [references\u002Fsdk-version-format.md](references\u002Fsdk-version-format.md).\n\n> ⚠️ **Servicing branches (2xx, 3xx)** do NOT source-build runtime. The script automatically follows the dependency chain through `Version.Details.xml` to the 1xx branch. See [references\u002Fservicing-topology.md](references\u002Fservicing-topology.md).\n\n## References\n\n- **Internal VMR branches**: See [references\u002Finternal-vmr.md](references\u002Finternal-vmr.md)\n- **SDK version format**: See [references\u002Fsdk-version-format.md](references\u002Fsdk-version-format.md)\n- **Servicing branch topology**: See [references\u002Fservicing-topology.md](references\u002Fservicing-topology.md)\n- **AzDO pipeline IDs and queries**: See [references\u002Fazdo-pipelines.md](references\u002Fazdo-pipelines.md)\n",{"data":28,"body":30},{"name":4,"description":6,"allowed-tools":29},"shell",{"type":31,"children":32},"root",[33,41,47,87,94,104,111,116,122,154,199,209,242,253,280,286,291,325,411,417,422,449,455,460,571,592,628,654,660,717],{"type":34,"tag":35,"props":36,"children":37},"element","h1",{"id":4},[38],{"type":39,"value":40},"text","Flow Tracing",{"type":34,"tag":42,"props":43,"children":44},"p",{},[45],{"type":39,"value":46},"Trace dependency flow across .NET repositories through the VMR pipeline. Two workflows:",{"type":34,"tag":48,"props":49,"children":50},"ol",{},[51,63],{"type":34,"tag":52,"props":53,"children":54},"li",{},[55,61],{"type":34,"tag":56,"props":57,"children":58},"strong",{},[59],{"type":39,"value":60},"Cross-repo flow trace",{"type":39,"value":62},": Has a change from repo A reached repo B? → Use Steps 1-4 below (reads GitHub files + maestro MCP directly)",{"type":34,"tag":52,"props":64,"children":65},{},[66,71,73,85],{"type":34,"tag":56,"props":67,"children":68},{},[69],{"type":39,"value":70},"SDK version trace",{"type":39,"value":72},": What component SHA is in a specific SDK version? → ",{"type":34,"tag":56,"props":74,"children":75},{},[76,78],{"type":39,"value":77},"Run ",{"type":34,"tag":79,"props":80,"children":82},"code",{"className":81},[],[83],{"type":39,"value":84},"Get-SdkVersionTrace.ps1",{"type":39,"value":86}," (handles version decoding, build lookup, and servicing topology automatically)",{"type":34,"tag":88,"props":89,"children":91},"h2",{"id":90},"cross-repo-flow-trace",[92],{"type":39,"value":93},"Cross-Repo Flow Trace",{"type":34,"tag":42,"props":95,"children":96},{},[97,102],{"type":34,"tag":56,"props":98,"children":99},{},[100],{"type":39,"value":101},"Question",{"type":39,"value":103},": \"Has change X from repo A reached repo B?\"",{"type":34,"tag":105,"props":106,"children":108},"h3",{"id":107},"step-1-resolve-the-source-change",[109],{"type":39,"value":110},"Step 1: Resolve the Source Change",{"type":34,"tag":42,"props":112,"children":113},{},[114],{"type":39,"value":115},"Identify the merge commit SHA in repo A from the PR number, issue number, commit SHA, or description the user provides. If the PR isn't merged yet, stop — the change hasn't entered the pipeline.",{"type":34,"tag":105,"props":117,"children":119},{"id":118},"step-2-check-vmr-intake-source-manifestjson",[120],{"type":39,"value":121},"Step 2: Check VMR Intake (source-manifest.json)",{"type":34,"tag":123,"props":124,"children":125},"blockquote",{},[126],{"type":34,"tag":42,"props":127,"children":128},{},[129,131,136,138,144,146,152],{"type":39,"value":130},"⚠️ ",{"type":34,"tag":56,"props":132,"children":133},{},[134],{"type":39,"value":135},"Internal branches",{"type":39,"value":137}," (",{"type":34,"tag":79,"props":139,"children":141},{"className":140},[],[142],{"type":39,"value":143},"internal\u002Frelease\u002F*",{"type":39,"value":145},") exist only on AzDO, not GitHub. Use the AzDO REST API to read files. See ",{"type":34,"tag":147,"props":148,"children":150},"a",{"href":149},"references\u002Finternal-vmr.md",[151],{"type":39,"value":149},{"type":39,"value":153},".",{"type":34,"tag":42,"props":155,"children":156},{},[157,159,165,167,173,175,181,183,189,191,197],{"type":39,"value":158},"Read ",{"type":34,"tag":79,"props":160,"children":162},{"className":161},[],[163],{"type":39,"value":164},"src\u002Fsource-manifest.json",{"type":39,"value":166}," from ",{"type":34,"tag":79,"props":168,"children":170},{"className":169},[],[171],{"type":39,"value":172},"dotnet\u002Fdotnet",{"type":39,"value":174}," on the target VMR branch (usually ",{"type":34,"tag":79,"props":176,"children":178},{"className":177},[],[179],{"type":39,"value":180},"main",{"type":39,"value":182}," or ",{"type":34,"tag":79,"props":184,"children":186},{"className":185},[],[187],{"type":39,"value":188},"release\u002F*",{"type":39,"value":190},"). This file is the authoritative record of what the VMR has actually consumed — subscription status reflects Maestro's bookkeeping, but the manifest reflects reality. Find the entry for repo A — the ",{"type":34,"tag":79,"props":192,"children":194},{"className":193},[],[195],{"type":39,"value":196},"commitSha",{"type":39,"value":198}," field shows the latest commit the VMR has consumed.",{"type":34,"tag":42,"props":200,"children":201},{},[202,207],{"type":34,"tag":56,"props":203,"children":204},{},[205],{"type":39,"value":206},"Determine if the change is included",{"type":39,"value":208}," (try in order):",{"type":34,"tag":48,"props":210,"children":211},{},[212,222,232],{"type":34,"tag":52,"props":213,"children":214},{},[215,220],{"type":34,"tag":56,"props":216,"children":217},{},[218],{"type":39,"value":219},"Date comparison",{"type":39,"value":221}," (fastest): If the VMR commit date is months after the PR merge date, it's included.",{"type":34,"tag":52,"props":223,"children":224},{},[225,230],{"type":34,"tag":56,"props":226,"children":227},{},[228],{"type":39,"value":229},"Compare API",{"type":39,"value":231},": Use GitHub compare endpoint if dates are close.",{"type":34,"tag":52,"props":233,"children":234},{},[235,240],{"type":34,"tag":56,"props":236,"children":237},{},[238],{"type":39,"value":239},"Commit history walk",{"type":39,"value":241},": List recent commits if compare is unavailable.",{"type":34,"tag":42,"props":243,"children":244},{},[245,247,252],{"type":39,"value":246},"If repo A's SHA in source-manifest is not past the merge commit → the change hasn't reached the VMR yet. Check for an open forward flow PR from repo A into ",{"type":34,"tag":79,"props":248,"children":250},{"className":249},[],[251],{"type":39,"value":172},{"type":39,"value":153},{"type":34,"tag":123,"props":254,"children":255},{},[256],{"type":34,"tag":42,"props":257,"children":258},{},[259,260,265,267,272,274,279],{"type":39,"value":130},{"type":34,"tag":56,"props":261,"children":262},{},[263],{"type":39,"value":264},"2xx\u002F3xx bands",{"type":39,"value":266},": Only the ",{"type":34,"tag":56,"props":268,"children":269},{},[270],{"type":39,"value":271},"1xx branch",{"type":39,"value":273}," source-builds all components. If tracing to a 2xx\u002F3xx branch, runtime\u002Faspnetcore won't appear in source-manifest — they're consumed as prebuilts from 1xx. See ",{"type":34,"tag":147,"props":275,"children":277},{"href":276},"references\u002Fservicing-topology.md",[278],{"type":39,"value":276},{"type":39,"value":153},{"type":34,"tag":105,"props":281,"children":283},{"id":282},"step-3-check-downstream-delivery-repo-b",[284],{"type":39,"value":285},"Step 3: Check Downstream Delivery (repo B)",{"type":34,"tag":42,"props":287,"children":288},{},[289],{"type":39,"value":290},"If the VMR has the change, check if it has flowed to repo B:",{"type":34,"tag":123,"props":292,"children":293},{},[294],{"type":34,"tag":42,"props":295,"children":296},{},[297,298,307,309,315,317,323],{"type":39,"value":130},{"type":34,"tag":56,"props":299,"children":300},{},[301],{"type":34,"tag":79,"props":302,"children":304},{"className":303},[],[305],{"type":39,"value":306},"eng\u002FVersion.Details.xml",{"type":39,"value":308}," is the file you want — it contains source dependency entries with ",{"type":34,"tag":79,"props":310,"children":312},{"className":311},[],[313],{"type":39,"value":314},"Sha",{"type":39,"value":316}," fields. Do NOT use ",{"type":34,"tag":79,"props":318,"children":320},{"className":319},[],[321],{"type":39,"value":322},"eng\u002FVersions.props",{"type":39,"value":324}," (that has NuGet package versions, not source SHAs).",{"type":34,"tag":48,"props":326,"children":327},{},[328,338,355,401],{"type":34,"tag":52,"props":329,"children":330},{},[331,336],{"type":34,"tag":56,"props":332,"children":333},{},[334],{"type":39,"value":335},"Check subscription health",{"type":39,"value":337}," for repo B using maestro MCP.",{"type":34,"tag":52,"props":339,"children":340},{},[341,346,348,353],{"type":34,"tag":56,"props":342,"children":343},{},[344],{"type":39,"value":345},"If current",{"type":39,"value":347},": The change has reached repo B. Confirm by reading ",{"type":34,"tag":79,"props":349,"children":351},{"className":350},[],[352],{"type":39,"value":306},{"type":39,"value":354}," in repo B.",{"type":34,"tag":52,"props":356,"children":357},{},[358,363,365,370,372,377,379,384,386,391,393,399],{"type":34,"tag":56,"props":359,"children":360},{},[361],{"type":39,"value":362},"If stale",{"type":39,"value":364},": Read ",{"type":34,"tag":79,"props":366,"children":368},{"className":367},[],[369],{"type":39,"value":306},{"type":39,"value":371}," in repo B — the ",{"type":34,"tag":79,"props":373,"children":375},{"className":374},[],[376],{"type":39,"value":172},{"type":39,"value":378}," entry's ",{"type":34,"tag":79,"props":380,"children":382},{"className":381},[],[383],{"type":39,"value":314},{"type":39,"value":385}," is the VMR commit repo B last consumed. Check ",{"type":34,"tag":79,"props":387,"children":389},{"className":388},[],[390],{"type":39,"value":164},{"type":39,"value":392}," at ",{"type":34,"tag":394,"props":395,"children":396},"em",{},[397],{"type":39,"value":398},"that SHA",{"type":39,"value":400}," for repo A's commitSha. If it's past the merge commit, the change reached repo B despite the stale subscription.",{"type":34,"tag":52,"props":402,"children":403},{},[404,409],{"type":34,"tag":56,"props":405,"children":406},{},[407],{"type":39,"value":408},"If stale AND change not in consumed VMR SHA",{"type":39,"value":410},": Change is in the VMR but hasn't flowed to repo B. Suggest flow-analysis skill for diagnosis.",{"type":34,"tag":105,"props":412,"children":414},{"id":413},"step-4-report",[415],{"type":39,"value":416},"Step 4: Report",{"type":34,"tag":42,"props":418,"children":419},{},[420],{"type":39,"value":421},"Summarize the trace chain:",{"type":34,"tag":423,"props":424,"children":425},"ul",{},[426,439,444],{"type":34,"tag":52,"props":427,"children":428},{},[429,431,437],{"type":39,"value":430},"\"✅ roslyn#80873 merged at ",{"type":34,"tag":79,"props":432,"children":434},{"className":433},[],[435],{"type":39,"value":436},"abc123",{"type":39,"value":438}," → VMR consumed it → runtime backflow current\"",{"type":34,"tag":52,"props":440,"children":441},{},[442],{"type":39,"value":443},"\"⚠️ Change in VMR → but runtime backflow is 3 builds behind\"",{"type":34,"tag":52,"props":445,"children":446},{},[447],{"type":39,"value":448},"\"❌ PR hasn't merged yet — not in pipeline\"",{"type":34,"tag":88,"props":450,"children":452},{"id":451},"sdk-version-trace",[453],{"type":39,"value":454},"SDK Version Trace",{"type":34,"tag":42,"props":456,"children":457},{},[458],{"type":39,"value":459},"Run the script to trace from an SDK version string to a component commit SHA:",{"type":34,"tag":461,"props":462,"children":467},"pre",{"className":463,"code":464,"language":465,"meta":466,"style":466},"language-powershell shiki shiki-themes material-theme-lighter material-theme material-theme-palenight","# Trace runtime SHA in a specific SDK version\n.\u002Fscripts\u002FGet-SdkVersionTrace.ps1 -SdkVersion \"10.0.300-preview.26117.103\"\n\n# Trace a specific component\n.\u002Fscripts\u002FGet-SdkVersionTrace.ps1 -SdkVersion \"10.0.300-preview.26117.103\" -Component \"aspnetcore\"\n\n# Check if specific commits are included\n.\u002Fscripts\u002FGet-SdkVersionTrace.ps1 -SdkVersion \"10.0.300-preview.26117.103\" -CheckCommit \"b226ba1f77a4\",\"f3bc0212e637\"\n\n# Just decode the version string\n.\u002Fscripts\u002FGet-SdkVersionTrace.ps1 -SdkVersion \"10.0.300-preview.26117.103\" -DecodeOnly\n","powershell","",[468],{"type":34,"tag":79,"props":469,"children":470},{"__ignoreMap":466},[471,482,491,501,510,519,527,536,545,553,562],{"type":34,"tag":472,"props":473,"children":476},"span",{"class":474,"line":475},"line",1,[477],{"type":34,"tag":472,"props":478,"children":479},{},[480],{"type":39,"value":481},"# Trace runtime SHA in a specific SDK version\n",{"type":34,"tag":472,"props":483,"children":485},{"class":474,"line":484},2,[486],{"type":34,"tag":472,"props":487,"children":488},{},[489],{"type":39,"value":490},".\u002Fscripts\u002FGet-SdkVersionTrace.ps1 -SdkVersion \"10.0.300-preview.26117.103\"\n",{"type":34,"tag":472,"props":492,"children":494},{"class":474,"line":493},3,[495],{"type":34,"tag":472,"props":496,"children":498},{"emptyLinePlaceholder":497},true,[499],{"type":39,"value":500},"\n",{"type":34,"tag":472,"props":502,"children":504},{"class":474,"line":503},4,[505],{"type":34,"tag":472,"props":506,"children":507},{},[508],{"type":39,"value":509},"# Trace a specific component\n",{"type":34,"tag":472,"props":511,"children":513},{"class":474,"line":512},5,[514],{"type":34,"tag":472,"props":515,"children":516},{},[517],{"type":39,"value":518},".\u002Fscripts\u002FGet-SdkVersionTrace.ps1 -SdkVersion \"10.0.300-preview.26117.103\" -Component \"aspnetcore\"\n",{"type":34,"tag":472,"props":520,"children":522},{"class":474,"line":521},6,[523],{"type":34,"tag":472,"props":524,"children":525},{"emptyLinePlaceholder":497},[526],{"type":39,"value":500},{"type":34,"tag":472,"props":528,"children":530},{"class":474,"line":529},7,[531],{"type":34,"tag":472,"props":532,"children":533},{},[534],{"type":39,"value":535},"# Check if specific commits are included\n",{"type":34,"tag":472,"props":537,"children":539},{"class":474,"line":538},8,[540],{"type":34,"tag":472,"props":541,"children":542},{},[543],{"type":39,"value":544},".\u002Fscripts\u002FGet-SdkVersionTrace.ps1 -SdkVersion \"10.0.300-preview.26117.103\" -CheckCommit \"b226ba1f77a4\",\"f3bc0212e637\"\n",{"type":34,"tag":472,"props":546,"children":548},{"class":474,"line":547},9,[549],{"type":34,"tag":472,"props":550,"children":551},{"emptyLinePlaceholder":497},[552],{"type":39,"value":500},{"type":34,"tag":472,"props":554,"children":556},{"class":474,"line":555},10,[557],{"type":34,"tag":472,"props":558,"children":559},{},[560],{"type":39,"value":561},"# Just decode the version string\n",{"type":34,"tag":472,"props":563,"children":565},{"class":474,"line":564},11,[566],{"type":34,"tag":472,"props":567,"children":568},{},[569],{"type":39,"value":570},".\u002Fscripts\u002FGet-SdkVersionTrace.ps1 -SdkVersion \"10.0.300-preview.26117.103\" -DecodeOnly\n",{"type":34,"tag":42,"props":572,"children":573},{},[574,576,582,584,590],{"type":39,"value":575},"The script decodes the SDK version, maps to a VMR branch, finds the build in AzDO, and walks the dependency chain through ",{"type":34,"tag":79,"props":577,"children":579},{"className":578},[],[580],{"type":39,"value":581},"source-manifest.json",{"type":39,"value":583}," (and ",{"type":34,"tag":79,"props":585,"children":587},{"className":586},[],[588],{"type":39,"value":589},"Version.Details.xml",{"type":39,"value":591}," for servicing branches that don't source-build all components).",{"type":34,"tag":123,"props":593,"children":594},{},[595],{"type":34,"tag":42,"props":596,"children":597},{},[598,599,604,606,612,614,620,622,627],{"type":39,"value":130},{"type":34,"tag":56,"props":600,"children":601},{},[602],{"type":39,"value":603},"SDK version dates use Arcade's SHORT_DATE formula",{"type":39,"value":605},": ",{"type":34,"tag":79,"props":607,"children":609},{"className":608},[],[610],{"type":39,"value":611},"YY*1000 + MM*50 + DD",{"type":39,"value":613}," (NOT YYDDD day-of-year). ",{"type":34,"tag":79,"props":615,"children":617},{"className":616},[],[618],{"type":39,"value":619},"26117",{"type":39,"value":621}," = Feb 17, 2026, NOT April 27. See ",{"type":34,"tag":147,"props":623,"children":625},{"href":624},"references\u002Fsdk-version-format.md",[626],{"type":39,"value":624},{"type":39,"value":153},{"type":34,"tag":123,"props":629,"children":630},{},[631],{"type":34,"tag":42,"props":632,"children":633},{},[634,635,640,642,647,649,653],{"type":39,"value":130},{"type":34,"tag":56,"props":636,"children":637},{},[638],{"type":39,"value":639},"Servicing branches (2xx, 3xx)",{"type":39,"value":641}," do NOT source-build runtime. The script automatically follows the dependency chain through ",{"type":34,"tag":79,"props":643,"children":645},{"className":644},[],[646],{"type":39,"value":589},{"type":39,"value":648}," to the 1xx branch. See ",{"type":34,"tag":147,"props":650,"children":651},{"href":276},[652],{"type":39,"value":276},{"type":39,"value":153},{"type":34,"tag":88,"props":655,"children":657},{"id":656},"references",[658],{"type":39,"value":659},"References",{"type":34,"tag":423,"props":661,"children":662},{},[663,677,690,703],{"type":34,"tag":52,"props":664,"children":665},{},[666,671,673],{"type":34,"tag":56,"props":667,"children":668},{},[669],{"type":39,"value":670},"Internal VMR branches",{"type":39,"value":672},": See ",{"type":34,"tag":147,"props":674,"children":675},{"href":149},[676],{"type":39,"value":149},{"type":34,"tag":52,"props":678,"children":679},{},[680,685,686],{"type":34,"tag":56,"props":681,"children":682},{},[683],{"type":39,"value":684},"SDK version format",{"type":39,"value":672},{"type":34,"tag":147,"props":687,"children":688},{"href":624},[689],{"type":39,"value":624},{"type":34,"tag":52,"props":691,"children":692},{},[693,698,699],{"type":34,"tag":56,"props":694,"children":695},{},[696],{"type":39,"value":697},"Servicing branch topology",{"type":39,"value":672},{"type":34,"tag":147,"props":700,"children":701},{"href":276},[702],{"type":39,"value":276},{"type":34,"tag":52,"props":704,"children":705},{},[706,711,712],{"type":34,"tag":56,"props":707,"children":708},{},[709],{"type":39,"value":710},"AzDO pipeline IDs and queries",{"type":39,"value":672},{"type":34,"tag":147,"props":713,"children":715},{"href":714},"references\u002Fazdo-pipelines.md",[716],{"type":39,"value":714},{"type":34,"tag":718,"props":719,"children":720},"style",{},[721],{"type":39,"value":722},"html .light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html.light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"items":724,"total":16},[725,744,757,774,787,804,808],{"slug":726,"name":726,"fn":727,"description":728,"org":729,"tags":730,"stars":16,"repoUrl":17,"updatedAt":743},"binskim-analysis","investigate BinSkim SDL security findings","Investigate BinSkim SDL findings from official pipelines — understand Guardian filtering, compare raw vs merged SARIF, decode portal results, and determine fix ownership. Use when asked about SDL scan results, portal findings, Guardian filtering, rule meanings, or discrepancies between local and official results. Also use when asked \"why does the portal show X\", \"what's filtered\", \"explain Guardian\", \"investigate SDL findings\", \"portal BA2008\", \"binskim failures in pipeline\", or \"what rules are required\". DO NOT USE FOR: running BinSkim locally (use binskim-scan), source code analysis (use CodeQL), or credential scanning (use CredScan).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[731,734,737,740],{"name":732,"slug":733,"type":15},".NET","net",{"name":735,"slug":736,"type":15},"Audit","audit",{"name":738,"slug":739,"type":15},"Code Analysis","code-analysis",{"name":741,"slug":742,"type":15},"Security","security","2026-07-12T08:23:11.212231",{"slug":745,"name":745,"fn":746,"description":747,"org":748,"tags":749,"stars":16,"repoUrl":17,"updatedAt":756},"binskim-scan","run BinSkim binary security analysis","Run BinSkim binary security analysis locally against a dotnet repository. Use when asked to scan binaries, check BinSkim compliance, verify a fix for a rule violation, or run a local SDL scan. Also use when asked \"run binskim\", \"binary security scan\", \"scan binaries\", \"check binskim\", \"verify my fix\", \"repro BA2008 locally\", or \"verify BA2008 fix\". DO NOT USE FOR: investigating official pipeline results or portal findings (use binskim-analysis), source code analysis (use CodeQL), credential scanning (use CredScan), or general build\u002Ftest failures (use ci-analysis).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[750,751,754,755],{"name":732,"slug":733,"type":15},{"name":752,"slug":753,"type":15},"CLI","cli",{"name":738,"slug":739,"type":15},{"name":741,"slug":742,"type":15},"2026-07-12T08:23:09.911458",{"slug":758,"name":758,"fn":759,"description":760,"org":761,"tags":762,"stars":16,"repoUrl":17,"updatedAt":773},"ci-analysis","analyze .NET CI build and test status","Analyze CI build and test status from Azure DevOps and Helix for dotnet repository PRs. Use when checking CI status, investigating failures, determining if a PR is ready to merge, or given URLs containing dev.azure.com or helix.dot.net. Also use when asked \"why is CI red\", \"test failures\", \"retry CI\", \"rerun tests\", \"is CI green\", \"build failed\", \"checks failing\", or \"flaky tests\". DO NOT USE FOR: investigating stale codeflow PRs or dependency update health, tracing whether a commit has flowed from one repo to another, reviewing code changes for correctness or style.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[763,764,767,770],{"name":732,"slug":733,"type":15},{"name":765,"slug":766,"type":15},"Azure","azure",{"name":768,"slug":769,"type":15},"CI\u002FCD","ci-cd",{"name":771,"slug":772,"type":15},"Debugging","debugging","2026-07-12T08:21:49.360882",{"slug":775,"name":775,"fn":776,"description":777,"org":778,"tags":779,"stars":16,"repoUrl":17,"updatedAt":786},"ci-crash-dump","debug CI crash dumps","Download and debug crash dumps from CI test failures in dotnet repositories. Use when a CI test crashed (not just failed), when the user wants to debug a crash dump from a PR or build, or when asked \"debug dump\", \"download dump\", \"crash dump from CI\", \"test crashed\", \"analyze crash in PR\", or \"why did the test crash\". DO NOT USE FOR: test failures that are not crashes (use ci-analysis), build failures, performance analysis, or analyzing dumps you already have locally.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[780,781,782,783],{"name":732,"slug":733,"type":15},{"name":768,"slug":769,"type":15},{"name":771,"slug":772,"type":15},{"name":784,"slug":785,"type":15},"Testing","testing","2026-07-12T08:21:56.945844",{"slug":788,"name":788,"fn":789,"description":790,"org":791,"tags":792,"stars":16,"repoUrl":17,"updatedAt":803},"flow-analysis","analyze VMR codeflow health","Analyze VMR codeflow health using maestro MCP tools and GitHub MCP tools. USE FOR: investigating stale codeflow PRs, checking if fixes have flowed through the VMR pipeline, debugging dependency update issues, checking overall flow status for a repo, diagnosing why backflow PRs are missing or blocked, subscription health, build freshness, URLs containing dotnet-maestro or \"Source code updates from dotnet\u002Fdotnet\". DO NOT USE FOR: CI build failures (use ci-analysis skill), code review (use code-review skill), general PR investigation without codeflow context, tracing whether a specific commit\u002FPR has reached another repo (use flow-tracing skill). INVOKES: maestro and GitHub MCP tools, flow-health.cs script.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[793,794,797,800],{"name":768,"slug":769,"type":15},{"name":795,"slug":796,"type":15},"Engineering","engineering",{"name":798,"slug":799,"type":15},"GitHub","github",{"name":801,"slug":802,"type":15},"MCP","mcp","2026-07-12T08:21:53.151866",{"slug":4,"name":4,"fn":5,"description":6,"org":805,"tags":806,"stars":16,"repoUrl":17,"updatedAt":18},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[807],{"name":13,"slug":14,"type":15},{"slug":809,"name":809,"fn":810,"description":811,"org":812,"tags":813,"stars":16,"repoUrl":17,"updatedAt":817},"helix-investigation","investigate Helix test failures","Deep-dive investigation of Helix test failures starting from AzDO build legs. USE FOR: investigating recurring Helix test failures, downloading and analyzing Helix console logs, comparing passing vs failing runs, identifying machine-specific issues, XHarness timeout analysis, Android emulator DEVICE_NOT_FOUND errors, bulk failure aggregation across legs, \"why does this test fail on some machines\", \"top 5 failing tests in the last 2 days\", \"download helix logs for build X\", \"compare passing and failing helix runs\", \"what are the most common failures\". DO NOT USE FOR: high-level CI status checks (use ci-analysis), codeflow PRs (use flow-analysis). INVOKES: Helix and AzDO MCP tools, curl, gh CLI.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[814,815,816],{"name":771,"slug":772,"type":15},{"name":795,"slug":796,"type":15},{"name":784,"slug":785,"type":15},"2026-07-12T08:21:46.445586",{"items":819,"total":978},[820,834,847,862,880,892,912,922,934,944,957,968],{"slug":821,"name":821,"fn":822,"description":823,"org":824,"tags":825,"stars":831,"repoUrl":832,"updatedAt":833},"multithreaded-task-migration","migrate MSBuild tasks to multithreaded mode","Guide for migrating MSBuild tasks to multithreaded mode support, including compatibility red-team review. Use this when converting tasks to thread-safe versions, implementing IMultiThreadableTask, adding TaskEnvironment support, or auditing migrations for behavioral compatibility.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[826,827,828],{"name":732,"slug":733,"type":15},{"name":795,"slug":796,"type":15},{"name":829,"slug":830,"type":15},"Performance","performance",5535,"https:\u002F\u002Fgithub.com\u002Fdotnet\u002Fmsbuild","2026-07-22T05:37:33.965588",{"slug":835,"name":835,"fn":836,"description":837,"org":838,"tags":839,"stars":844,"repoUrl":845,"updatedAt":846},"analyzing-dotnet-performance","analyze .NET code for performance anti-patterns","Scans .NET code for ~50 performance anti-patterns across async, memory, strings, collections, LINQ, regex, serialization, and I\u002FO with tiered severity classification. Use when analyzing .NET code for optimization opportunities, reviewing hot paths, or auditing allocation-heavy patterns.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[840,841,842,843],{"name":732,"slug":733,"type":15},{"name":738,"slug":739,"type":15},{"name":771,"slug":772,"type":15},{"name":829,"slug":830,"type":15},4576,"https:\u002F\u002Fgithub.com\u002Fdotnet\u002Fskills","2026-07-12T08:23:25.400375",{"slug":848,"name":848,"fn":849,"description":850,"org":851,"tags":852,"stars":844,"repoUrl":845,"updatedAt":861},"android-tombstone-symbolication","symbolicate .NET runtime frames in Android tombstones","Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app crash from a tombstone, resolving native backtrace frames in libmonosgen-2.0.so or libcoreclr.so to .NET runtime source code, or investigating SIGABRT, SIGSEGV, or other native signals originating from the .NET runtime on Android. DO NOT USE FOR pure Java\u002FKotlin crashes, managed .NET exceptions that are already captured in logcat, or iOS crash logs. INVOKES Symbolicate-Tombstone.ps1 script, llvm-symbolizer, Microsoft symbol server.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[853,854,857,858],{"name":732,"slug":733,"type":15},{"name":855,"slug":856,"type":15},"Android","android",{"name":771,"slug":772,"type":15},{"name":859,"slug":860,"type":15},"Microsoft","microsoft","2026-07-12T08:23:21.595572",{"slug":863,"name":863,"fn":864,"description":865,"org":866,"tags":867,"stars":844,"repoUrl":845,"updatedAt":879},"apple-crash-symbolication","symbolicate .NET runtime frames in crash logs","Symbolicate .NET runtime frames in Apple platform .ips crash logs (iOS, tvOS, Mac Catalyst, macOS). Extracts UUIDs and addresses from the native backtrace, locates dSYM debug symbols, and runs atos to produce function names with source file and line numbers. Automatically downloads .dwarf symbols from the Microsoft symbol server using Mach-O UUIDs. USE FOR triaging a .NET MAUI or Mono app crash from an .ips file on any Apple platform, resolving native backtrace frames in libcoreclr or libmonosgen-2.0 to .NET runtime source code, retrieving .ips crash logs from a connected iOS device or iPhone, or investigating EXC_CRASH, EXC_BAD_ACCESS, SIGABRT, or SIGSEGV originating from the .NET runtime. DO NOT USE FOR pure Swift\u002FObjective-C crashes with no .NET components, or Android tombstone files. INVOKES Symbolicate-Crash.ps1 script, atos, dwarfdump, idevicecrashreport.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[868,869,870,873,876],{"name":732,"slug":733,"type":15},{"name":771,"slug":772,"type":15},{"name":871,"slug":872,"type":15},"iOS","ios",{"name":874,"slug":875,"type":15},"macOS","macos",{"name":877,"slug":878,"type":15},"Observability","observability","2026-07-12T08:23:20.369986",{"slug":881,"name":881,"fn":882,"description":883,"org":884,"tags":885,"stars":844,"repoUrl":845,"updatedAt":891},"assertion-quality","evaluate assertion quality in test suites","Analyzes the variety and depth of assertions across test suites in any language. Use when the user asks to evaluate assertion quality, find shallow tests, identify assertion-free tests (no assertions or only trivial ones like Assert.IsNotNull \u002F toBeTruthy()), flag self-referential or tautological assertions, measure assertion diversity, or audit whether tests verify different facets of behavior. Polyglot: .NET, Python, TS\u002FJS, Java, Go, Ruby, Rust, Swift, Kotlin, PowerShell, C++. DO NOT USE FOR: writing new tests (use code-testing-agent \u002F writing-mstest-tests), mutation reasoning about whether tests would catch a bug (use test-gap-analysis), or a general severity-ranked anti-pattern audit (use test-anti-patterns), fixing or rewriting assertions, or writing, fixing, or modernizing MSTest tests, assertions, or attributes (use writing-mstest-tests).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[886,887,890],{"name":738,"slug":739,"type":15},{"name":888,"slug":889,"type":15},"QA","qa",{"name":784,"slug":785,"type":15},"2026-07-12T08:23:51.277743",{"slug":893,"name":893,"fn":894,"description":895,"org":896,"tags":897,"stars":844,"repoUrl":845,"updatedAt":911},"author-component","create and review Blazor components","Create or review Blazor components (.razor files) with correct architecture. USE FOR: writing new Blazor components that do NOT involve JavaScript interop, implementing parameters and EventCallback, RenderFragment slots, component lifecycle (OnInitializedAsync, OnParametersSet), async patterns, IAsyncDisposable, CancellationToken, CSS isolation, code-behind. DO NOT USE FOR: creating new projects (use create-blazor-project), JavaScript interop or calling browser APIs from Blazor (use use-js-interop), forms and validation (use collect-user-input), prerendering issues (use support-prerendering), HTTP data fetching patterns (use fetch-and-send-data), coordinating state between unrelated components (use coordinate-components).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[898,899,902,905,908],{"name":732,"slug":733,"type":15},{"name":900,"slug":901,"type":15},"Blazor","blazor",{"name":903,"slug":904,"type":15},"C#","csharp",{"name":906,"slug":907,"type":15},"UI Components","ui-components",{"name":909,"slug":910,"type":15},"Web Development","web-development","2026-07-15T06:03:29.216359",{"slug":913,"name":913,"fn":914,"description":915,"org":916,"tags":917,"stars":844,"repoUrl":845,"updatedAt":921},"binlog-failure-analysis","analyze MSBuild binary logs","Analyze MSBuild binary logs to diagnose build failures. USE FOR: build errors that are unclear from console output, diagnosing cascading failures across multi-project builds, tracing MSBuild target execution order, and generally any MSBuild build issues. Requires an existing .binlog file. DO NOT USE FOR: generating binlogs (use binlog-generation), non-MSBuild build systems.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[918,919,920],{"name":738,"slug":739,"type":15},{"name":771,"slug":772,"type":15},{"name":859,"slug":860,"type":15},"2026-07-12T08:21:34.637923",{"slug":923,"name":923,"fn":924,"description":925,"org":926,"tags":927,"stars":844,"repoUrl":845,"updatedAt":933},"binlog-generation","generate MSBuild binary logs for diagnostics","Generate MSBuild binary logs (binlogs) for build diagnostics and analysis. USE FOR: adding \u002Fbl:{} to any dotnet build, test, pack, publish, or restore command to capture a full build execution trace, prerequisite for binlog-failure-analysis and build-perf-diagnostics skills, enabling post-build investigation of errors or performance. Requires MSBuild 17.8+ \u002F .NET 8 SDK+ for {} placeholder; PowerShell needs -bl:{{}}. DO NOT USE FOR: non-MSBuild build systems (npm, Maven, CMake), analyzing an existing binlog (use binlog-failure-analysis instead).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[928,931,932],{"name":929,"slug":930,"type":15},"Build","build",{"name":771,"slug":772,"type":15},{"name":795,"slug":796,"type":15},"2026-07-19T05:38:19.340791",{"slug":935,"name":935,"fn":936,"description":937,"org":938,"tags":939,"stars":844,"repoUrl":845,"updatedAt":943},"build-parallelism","optimize MSBuild build parallelism","Diagnose and fix under-parallelized MSBuild builds. USE WHEN a multi-project solution build is slower than expected, doesn't speed up when you add cores, pegs a single core while others idle, or you want to know why `-m` isn't helping. Note: `\u002Fmaxcpucount` default is 1 (sequential) — always pass `-m` for parallel builds. Covers finding the critical path (longest serial ProjectReference chain), graph build (`\u002Fgraph`), BuildInParallel, and solution filters (`.slnf`). DO NOT USE FOR: single-project builds, incremental issues (use incremental-build), compilation slowness inside one project (use build-perf-diagnostics), non-MSBuild build systems.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[940,941,942],{"name":732,"slug":733,"type":15},{"name":795,"slug":796,"type":15},{"name":829,"slug":830,"type":15},"2026-07-19T05:38:18.364937",{"slug":945,"name":945,"fn":946,"description":947,"org":948,"tags":949,"stars":844,"repoUrl":845,"updatedAt":956},"build-perf-baseline","establish and optimize build performance baselines","Establish build performance baselines and apply systematic optimization techniques. USE FOR: diagnosing slow builds, establishing before\u002Fafter measurements (cold, warm, no-op scenarios), applying optimization strategies like MSBuild Server, static graph builds, artifacts output, and dependency graph trimming. Start here before diving into build-perf-diagnostics, incremental-build, or build-parallelism. DO NOT USE FOR: non-MSBuild build systems, detailed bottleneck analysis (use build-perf-diagnostics after baselining).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[950,951,954,955],{"name":795,"slug":796,"type":15},{"name":952,"slug":953,"type":15},"Monitoring","monitoring",{"name":829,"slug":830,"type":15},{"name":784,"slug":785,"type":15},"2026-07-12T08:21:35.865649",{"slug":958,"name":958,"fn":959,"description":960,"org":961,"tags":962,"stars":844,"repoUrl":845,"updatedAt":967},"build-perf-diagnostics","diagnose MSBuild build performance bottlenecks","Diagnose MSBuild build performance bottlenecks using binary log analysis. USE FOR: identifying why builds are slow by analyzing binlog performance summaries, detecting ResolveAssemblyReference (RAR) taking >5s, Roslyn analyzers consuming >30% of Csc time, single targets dominating >50% of build time, node utilization below 80%, excessive Copy tasks, NuGet restore running every build. Covers timeline analysis, Target\u002FTask Performance Summary interpretation, and 7 common bottleneck categories. Use after build-perf-baseline has established measurements. DO NOT USE FOR: establishing initial baselines (use build-perf-baseline first), fixing incremental build issues (use incremental-build), parallelism tuning (use build-parallelism), non-MSBuild build systems.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[963,964,965,966],{"name":732,"slug":733,"type":15},{"name":771,"slug":772,"type":15},{"name":795,"slug":796,"type":15},{"name":829,"slug":830,"type":15},"2026-07-12T08:21:40.961722",{"slug":969,"name":969,"fn":970,"description":971,"org":972,"tags":973,"stars":844,"repoUrl":845,"updatedAt":977},"check-bin-obj-clash","detect MSBuild output path conflicts","Detects MSBuild projects with conflicting OutputPath or IntermediateOutputPath. USE FOR: builds failing with 'Cannot create a file when that file already exists', 'The process cannot access the file because it is being used by another process', intermittent build failures that succeed on retry, or missing\u002Foverwritten outputs in multi-project or multi-targeting builds where bin\u002Fobj (or project.assets.json) collide. Common causes: shared OutputPath, missing AppendTargetFrameworkToOutputPath, extra global properties (e.g. PublishReadyToRun), or SetTargetFramework on a ProjectReference to a single-targeting project. DO NOT USE FOR: file access errors unrelated to MSBuild (OS-level locking), single-project single-TFM builds, non-MSBuild build systems.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[974,975,976],{"name":771,"slug":772,"type":15},{"name":795,"slug":796,"type":15},{"name":888,"slug":889,"type":15},"2026-07-19T05:38:14.336279",144]