[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-dotnet-including-generated-files":3,"mdc--9wzoci-key":34,"related-repo-dotnet-including-generated-files":993,"related-org-dotnet-including-generated-files":1100},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":22,"repoUrl":23,"updatedAt":24,"license":25,"forks":26,"topics":27,"repo":29,"sourceUrl":32,"mdContent":33},"including-generated-files","fix generated file inclusion in MSBuild","Fix MSBuild targets that generate files during the build but those files are missing from compilation or output. USE FOR: generated source files not compiling (CS0246 for a type that should exist), custom build tasks that create files but they are invisible to subsequent targets, globs not capturing build-generated files because they expand at evaluation time before execution creates them, ensuring generated files are cleaned by the Clean target. Covers correct BeforeTargets timing (CoreCompile, BeforeBuild, AssignTargetPaths), adding to Compile\u002FFileWrites item groups, using $(IntermediateOutputPath) instead of hardcoded obj\u002F paths. DO NOT USE FOR: C# source generators that already work via the Roslyn pipeline, T4 design-time generation that runs in Visual Studio, non-MSBuild build systems.",{"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,16,19],{"name":13,"slug":14,"type":15},"Build","build","tag",{"name":17,"slug":18,"type":15},".NET","net",{"name":20,"slug":21,"type":15},"Debugging","debugging",4576,"https:\u002F\u002Fgithub.com\u002Fdotnet\u002Fskills","2026-07-15T06:03:24.215164","MIT",332,[28],"agent-skills",{"repoUrl":23,"stars":22,"forks":26,"topics":30,"description":31},[28],"Repository for skills to assist AI coding agents with .NET and C#","https:\u002F\u002Fgithub.com\u002Fdotnet\u002Fskills\u002Ftree\u002FHEAD\u002Fplugins\u002Fdotnet-msbuild\u002Fskills\u002Fincluding-generated-files","---\nname: including-generated-files\ndescription: \"Fix MSBuild targets that generate files during the build but those files are missing from compilation or output. USE FOR: generated source files not compiling (CS0246 for a type that should exist), custom build tasks that create files but they are invisible to subsequent targets, globs not capturing build-generated files because they expand at evaluation time before execution creates them, ensuring generated files are cleaned by the Clean target. Covers correct BeforeTargets timing (CoreCompile, BeforeBuild, AssignTargetPaths), adding to Compile\u002FFileWrites item groups, using $(IntermediateOutputPath) instead of hardcoded obj\u002F paths. DO NOT USE FOR: C# source generators that already work via the Roslyn pipeline, T4 design-time generation that runs in Visual Studio, non-MSBuild build systems.\"\nlicense: MIT\n---\n\n# Including Generated Files Into Your Build\n\n## Overview\n\nFiles generated during the build are generally ignored by the build process. This leads to confusing results such as:\n- Generated files not being included in the output directory\n- Generated source files not being compiled\n- Globs not capturing files created during the build\n\nThis happens because of how MSBuild's build phases work.\n\n## Quick Takeaway\n\nFor code files generated during the build - we need to add those to `Compile` and `FileWrites` item groups within the target generating the file(s):\n\n```xml\n  \u003CItemGroup>\n    \u003CCompile Include=\"$(GeneratedFilePath)\" \u002F>\n    \u003CFileWrites Include=\"$(GeneratedFilePath)\" \u002F>\n  \u003C\u002FItemGroup>\n```\n\nThe target generating the file(s) should be hooked before CoreCompile and BeforeCompile targets - `BeforeTargets=\"CoreCompile;BeforeCompile\"`\n\n## Why Generated Files Are Ignored\n\nFor detailed explanation, see [How MSBuild Builds Projects](https:\u002F\u002Fdocs.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fbuild-process-overview).\n\n### Evaluation Phase\n\nMSBuild reads your project, imports everything, creates Properties, expands globs for Items **outside of Targets**, and sets up the build process.\n\n### Execution Phase\n\nMSBuild runs Targets & Tasks with the provided Properties & Items to perform the build.\n\n**Key Takeaway:** Files generated during execution don't exist during evaluation, therefore they aren't found. This particularly affects files that are globbed by default, such as source files (`.cs`).\n\n## Solution: Manually Add Generated Files\n\nWhen files are generated during the build, manually add them into the build process. The approach depends on the type of file being generated.\n\n### Use `$(IntermediateOutputPath)` for Generated File Location\n\nAlways use `$(IntermediateOutputPath)` as the base directory for generated files. **Do not** hardcode `obj\\` or construct the intermediary path manually (e.g., `obj\\$(Configuration)\\$(TargetFramework)\\`). The intermediate output path can be redirected to a different location in some build configurations (e.g., shared output directories, CI environments). Using `$(IntermediateOutputPath)` ensures your target works correctly regardless of the actual path.\n\n### Always Add Generated Files to `FileWrites`\n\nEvery generated file should be added to the `FileWrites` item group. This ensures that MSBuild's `Clean` target properly removes your generated files. Without this, generated files will accumulate as stale artifacts across builds.\n\n```xml\n\u003CItemGroup>\n  \u003CFileWrites Include=\"$(IntermediateOutputPath)my-generated-file.xyz\" \u002F>\n\u003C\u002FItemGroup>\n```\n\n### Basic Pattern (Non-Code Files)\n\nFor generated files that need to be copied to output (config files, data files, etc.), add them to `Content` or `None` items before `BeforeBuild`:\n\n```xml\n\u003CTarget Name=\"IncludeGeneratedFiles\" BeforeTargets=\"BeforeBuild\">\n  \n  \u003C!-- Your logic that generates files goes here -->\n\n  \u003CItemGroup>\n    \u003CNone Include=\"$(IntermediateOutputPath)my-generated-file.xyz\" CopyToOutputDirectory=\"PreserveNewest\"\u002F>\n    \n    \u003C!-- Capture all files of a certain type with a glob -->\n    \u003CNone Include=\"$(IntermediateOutputPath)generated\\*.xyz\" CopyToOutputDirectory=\"PreserveNewest\"\u002F>\n\n    \u003C!-- Register generated files for proper cleanup -->\n    \u003CFileWrites Include=\"$(IntermediateOutputPath)my-generated-file.xyz\" \u002F>\n    \u003CFileWrites Include=\"$(IntermediateOutputPath)generated\\*.xyz\" \u002F>\n  \u003C\u002FItemGroup>\n\u003C\u002FTarget>\n```\n\n### For Generated Source Files (Code That Needs Compilation)\n\nIf you're generating `.cs` files that need to be compiled, use **`BeforeTargets=\"CoreCompile;BeforeCompile\"`**. This is the correct timing for adding `Compile` items — it runs late enough that the file generation has occurred, but before the compiler runs. Using `BeforeBuild` is too early for some scenarios and may not work reliably with all SDK features.\n\n```xml\n\u003CTarget Name=\"IncludeGeneratedSourceFiles\" BeforeTargets=\"CoreCompile;BeforeCompile\">\n  \u003CPropertyGroup>\n    \u003CGeneratedCodeDir>$(IntermediateOutputPath)Generated\\\u003C\u002FGeneratedCodeDir>\n    \u003CGeneratedFilePath>$(GeneratedCodeDir)MyGeneratedFile.cs\u003C\u002FGeneratedFilePath>\n  \u003C\u002FPropertyGroup>\n\n  \u003CMakeDir Directories=\"$(GeneratedCodeDir)\" \u002F>\n\n  \u003C!-- Your logic that generates the .cs file goes here -->\n\n  \u003CItemGroup>\n    \u003CCompile Include=\"$(GeneratedFilePath)\" \u002F>\n    \u003CFileWrites Include=\"$(GeneratedFilePath)\" \u002F>\n  \u003C\u002FItemGroup>\n\u003C\u002FTarget>\n```\n\nNote: Specifying both `CoreCompile` and `BeforeCompile` ensures the target runs before whichever target comes first, providing robust ordering regardless of customizations in the build.\n\n## Target Timing\n\nChoose the `BeforeTargets` value based on the type of file being generated:\n\n- **`BeforeTargets=\"BeforeBuild\"`** — For non-code files added to `None` or `Content`. Runs early enough for copy-to-output scenarios.\n- **`BeforeTargets=\"CoreCompile;BeforeCompile\"`** — For generated source files added to `Compile`. Ensures the file is included before the compiler runs.\n- **`BeforeTargets=\"AssignTargetPaths\"`** — The \"final stop\" before `None` and `Content` items (among others) are transformed into new items. Use as a fallback if `BeforeBuild` is too early.\n\n## Globbing Behavior\n\nGlobs behave according to **when** the glob took place:\n\n| Glob Location | Files Captured |\n|---------------|----------------|\n| Outside of a target | Only files visible during Evaluation phase (before build starts) |\n| Inside of a target | Files visible when the target runs (can capture generated files if timed correctly) |\n\nThis is why the solution places the `\u003CItemGroup>` inside a `\u003CTarget>` - the glob runs during execution when the generated files exist.\n\n## Relevant Links\n\n- [How MSBuild Builds Projects](https:\u002F\u002Fdocs.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fbuild-process-overview)\n- [Evaluation Phase](https:\u002F\u002Fdocs.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fbuild-process-overview#evaluation-phase)\n- [Execution Phase](https:\u002F\u002Fdocs.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fbuild-process-overview#execution-phase)\n- [Common Item Types](https:\u002F\u002Fdocs.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fcommon-msbuild-project-items)\n- [How the SDK imports items by default](https:\u002F\u002Fgithub.com\u002Fdotnet\u002Fsdk\u002Fblob\u002Fmain\u002Fsrc\u002FTasks\u002FMicrosoft.NET.Build.Tasks\u002Ftargets\u002FMicrosoft.NET.Sdk.DefaultItems.props)\n- [Official docs: Handle generated files](https:\u002F\u002Flearn.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fcustomize-your-build#handle-generated-files)\n",{"data":35,"body":36},{"name":4,"description":6,"license":25},{"type":37,"children":38},"root",[39,48,55,61,81,86,92,114,163,174,180,196,203,216,222,227,245,251,256,270,312,323,343,374,380,409,545,551,587,706,726,732,745,829,835,847,901,922,928,987],{"type":40,"tag":41,"props":42,"children":44},"element","h1",{"id":43},"including-generated-files-into-your-build",[45],{"type":46,"value":47},"text","Including Generated Files Into Your Build",{"type":40,"tag":49,"props":50,"children":52},"h2",{"id":51},"overview",[53],{"type":46,"value":54},"Overview",{"type":40,"tag":56,"props":57,"children":58},"p",{},[59],{"type":46,"value":60},"Files generated during the build are generally ignored by the build process. This leads to confusing results such as:",{"type":40,"tag":62,"props":63,"children":64},"ul",{},[65,71,76],{"type":40,"tag":66,"props":67,"children":68},"li",{},[69],{"type":46,"value":70},"Generated files not being included in the output directory",{"type":40,"tag":66,"props":72,"children":73},{},[74],{"type":46,"value":75},"Generated source files not being compiled",{"type":40,"tag":66,"props":77,"children":78},{},[79],{"type":46,"value":80},"Globs not capturing files created during the build",{"type":40,"tag":56,"props":82,"children":83},{},[84],{"type":46,"value":85},"This happens because of how MSBuild's build phases work.",{"type":40,"tag":49,"props":87,"children":89},{"id":88},"quick-takeaway",[90],{"type":46,"value":91},"Quick Takeaway",{"type":40,"tag":56,"props":93,"children":94},{},[95,97,104,106,112],{"type":46,"value":96},"For code files generated during the build - we need to add those to ",{"type":40,"tag":98,"props":99,"children":101},"code",{"className":100},[],[102],{"type":46,"value":103},"Compile",{"type":46,"value":105}," and ",{"type":40,"tag":98,"props":107,"children":109},{"className":108},[],[110],{"type":46,"value":111},"FileWrites",{"type":46,"value":113}," item groups within the target generating the file(s):",{"type":40,"tag":115,"props":116,"children":121},"pre",{"className":117,"code":118,"language":119,"meta":120,"style":120},"language-xml shiki shiki-themes material-theme-lighter material-theme material-theme-palenight","  \u003CItemGroup>\n    \u003CCompile Include=\"$(GeneratedFilePath)\" \u002F>\n    \u003CFileWrites Include=\"$(GeneratedFilePath)\" \u002F>\n  \u003C\u002FItemGroup>\n","xml","",[122],{"type":40,"tag":98,"props":123,"children":124},{"__ignoreMap":120},[125,136,145,154],{"type":40,"tag":126,"props":127,"children":130},"span",{"class":128,"line":129},"line",1,[131],{"type":40,"tag":126,"props":132,"children":133},{},[134],{"type":46,"value":135},"  \u003CItemGroup>\n",{"type":40,"tag":126,"props":137,"children":139},{"class":128,"line":138},2,[140],{"type":40,"tag":126,"props":141,"children":142},{},[143],{"type":46,"value":144},"    \u003CCompile Include=\"$(GeneratedFilePath)\" \u002F>\n",{"type":40,"tag":126,"props":146,"children":148},{"class":128,"line":147},3,[149],{"type":40,"tag":126,"props":150,"children":151},{},[152],{"type":46,"value":153},"    \u003CFileWrites Include=\"$(GeneratedFilePath)\" \u002F>\n",{"type":40,"tag":126,"props":155,"children":157},{"class":128,"line":156},4,[158],{"type":40,"tag":126,"props":159,"children":160},{},[161],{"type":46,"value":162},"  \u003C\u002FItemGroup>\n",{"type":40,"tag":56,"props":164,"children":165},{},[166,168],{"type":46,"value":167},"The target generating the file(s) should be hooked before CoreCompile and BeforeCompile targets - ",{"type":40,"tag":98,"props":169,"children":171},{"className":170},[],[172],{"type":46,"value":173},"BeforeTargets=\"CoreCompile;BeforeCompile\"",{"type":40,"tag":49,"props":175,"children":177},{"id":176},"why-generated-files-are-ignored",[178],{"type":46,"value":179},"Why Generated Files Are Ignored",{"type":40,"tag":56,"props":181,"children":182},{},[183,185,194],{"type":46,"value":184},"For detailed explanation, see ",{"type":40,"tag":186,"props":187,"children":191},"a",{"href":188,"rel":189},"https:\u002F\u002Fdocs.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fbuild-process-overview",[190],"nofollow",[192],{"type":46,"value":193},"How MSBuild Builds Projects",{"type":46,"value":195},".",{"type":40,"tag":197,"props":198,"children":200},"h3",{"id":199},"evaluation-phase",[201],{"type":46,"value":202},"Evaluation Phase",{"type":40,"tag":56,"props":204,"children":205},{},[206,208,214],{"type":46,"value":207},"MSBuild reads your project, imports everything, creates Properties, expands globs for Items ",{"type":40,"tag":209,"props":210,"children":211},"strong",{},[212],{"type":46,"value":213},"outside of Targets",{"type":46,"value":215},", and sets up the build process.",{"type":40,"tag":197,"props":217,"children":219},{"id":218},"execution-phase",[220],{"type":46,"value":221},"Execution Phase",{"type":40,"tag":56,"props":223,"children":224},{},[225],{"type":46,"value":226},"MSBuild runs Targets & Tasks with the provided Properties & Items to perform the build.",{"type":40,"tag":56,"props":228,"children":229},{},[230,235,237,243],{"type":40,"tag":209,"props":231,"children":232},{},[233],{"type":46,"value":234},"Key Takeaway:",{"type":46,"value":236}," Files generated during execution don't exist during evaluation, therefore they aren't found. This particularly affects files that are globbed by default, such as source files (",{"type":40,"tag":98,"props":238,"children":240},{"className":239},[],[241],{"type":46,"value":242},".cs",{"type":46,"value":244},").",{"type":40,"tag":49,"props":246,"children":248},{"id":247},"solution-manually-add-generated-files",[249],{"type":46,"value":250},"Solution: Manually Add Generated Files",{"type":40,"tag":56,"props":252,"children":253},{},[254],{"type":46,"value":255},"When files are generated during the build, manually add them into the build process. The approach depends on the type of file being generated.",{"type":40,"tag":197,"props":257,"children":259},{"id":258},"use-intermediateoutputpath-for-generated-file-location",[260,262,268],{"type":46,"value":261},"Use ",{"type":40,"tag":98,"props":263,"children":265},{"className":264},[],[266],{"type":46,"value":267},"$(IntermediateOutputPath)",{"type":46,"value":269}," for Generated File Location",{"type":40,"tag":56,"props":271,"children":272},{},[273,275,280,282,287,289,295,297,303,305,310],{"type":46,"value":274},"Always use ",{"type":40,"tag":98,"props":276,"children":278},{"className":277},[],[279],{"type":46,"value":267},{"type":46,"value":281}," as the base directory for generated files. ",{"type":40,"tag":209,"props":283,"children":284},{},[285],{"type":46,"value":286},"Do not",{"type":46,"value":288}," hardcode ",{"type":40,"tag":98,"props":290,"children":292},{"className":291},[],[293],{"type":46,"value":294},"obj\\",{"type":46,"value":296}," or construct the intermediary path manually (e.g., ",{"type":40,"tag":98,"props":298,"children":300},{"className":299},[],[301],{"type":46,"value":302},"obj\\$(Configuration)\\$(TargetFramework)\\",{"type":46,"value":304},"). The intermediate output path can be redirected to a different location in some build configurations (e.g., shared output directories, CI environments). Using ",{"type":40,"tag":98,"props":306,"children":308},{"className":307},[],[309],{"type":46,"value":267},{"type":46,"value":311}," ensures your target works correctly regardless of the actual path.",{"type":40,"tag":197,"props":313,"children":315},{"id":314},"always-add-generated-files-to-filewrites",[316,318],{"type":46,"value":317},"Always Add Generated Files to ",{"type":40,"tag":98,"props":319,"children":321},{"className":320},[],[322],{"type":46,"value":111},{"type":40,"tag":56,"props":324,"children":325},{},[326,328,333,335,341],{"type":46,"value":327},"Every generated file should be added to the ",{"type":40,"tag":98,"props":329,"children":331},{"className":330},[],[332],{"type":46,"value":111},{"type":46,"value":334}," item group. This ensures that MSBuild's ",{"type":40,"tag":98,"props":336,"children":338},{"className":337},[],[339],{"type":46,"value":340},"Clean",{"type":46,"value":342}," target properly removes your generated files. Without this, generated files will accumulate as stale artifacts across builds.",{"type":40,"tag":115,"props":344,"children":346},{"className":117,"code":345,"language":119,"meta":120,"style":120},"\u003CItemGroup>\n  \u003CFileWrites Include=\"$(IntermediateOutputPath)my-generated-file.xyz\" \u002F>\n\u003C\u002FItemGroup>\n",[347],{"type":40,"tag":98,"props":348,"children":349},{"__ignoreMap":120},[350,358,366],{"type":40,"tag":126,"props":351,"children":352},{"class":128,"line":129},[353],{"type":40,"tag":126,"props":354,"children":355},{},[356],{"type":46,"value":357},"\u003CItemGroup>\n",{"type":40,"tag":126,"props":359,"children":360},{"class":128,"line":138},[361],{"type":40,"tag":126,"props":362,"children":363},{},[364],{"type":46,"value":365},"  \u003CFileWrites Include=\"$(IntermediateOutputPath)my-generated-file.xyz\" \u002F>\n",{"type":40,"tag":126,"props":367,"children":368},{"class":128,"line":147},[369],{"type":40,"tag":126,"props":370,"children":371},{},[372],{"type":46,"value":373},"\u003C\u002FItemGroup>\n",{"type":40,"tag":197,"props":375,"children":377},{"id":376},"basic-pattern-non-code-files",[378],{"type":46,"value":379},"Basic Pattern (Non-Code Files)",{"type":40,"tag":56,"props":381,"children":382},{},[383,385,391,393,399,401,407],{"type":46,"value":384},"For generated files that need to be copied to output (config files, data files, etc.), add them to ",{"type":40,"tag":98,"props":386,"children":388},{"className":387},[],[389],{"type":46,"value":390},"Content",{"type":46,"value":392}," or ",{"type":40,"tag":98,"props":394,"children":396},{"className":395},[],[397],{"type":46,"value":398},"None",{"type":46,"value":400}," items before ",{"type":40,"tag":98,"props":402,"children":404},{"className":403},[],[405],{"type":46,"value":406},"BeforeBuild",{"type":46,"value":408},":",{"type":40,"tag":115,"props":410,"children":412},{"className":117,"code":411,"language":119,"meta":120,"style":120},"\u003CTarget Name=\"IncludeGeneratedFiles\" BeforeTargets=\"BeforeBuild\">\n  \n  \u003C!-- Your logic that generates files goes here -->\n\n  \u003CItemGroup>\n    \u003CNone Include=\"$(IntermediateOutputPath)my-generated-file.xyz\" CopyToOutputDirectory=\"PreserveNewest\"\u002F>\n    \n    \u003C!-- Capture all files of a certain type with a glob -->\n    \u003CNone Include=\"$(IntermediateOutputPath)generated\\*.xyz\" CopyToOutputDirectory=\"PreserveNewest\"\u002F>\n\n    \u003C!-- Register generated files for proper cleanup -->\n    \u003CFileWrites Include=\"$(IntermediateOutputPath)my-generated-file.xyz\" \u002F>\n    \u003CFileWrites Include=\"$(IntermediateOutputPath)generated\\*.xyz\" \u002F>\n  \u003C\u002FItemGroup>\n\u003C\u002FTarget>\n",[413],{"type":40,"tag":98,"props":414,"children":415},{"__ignoreMap":120},[416,424,432,440,449,457,466,475,484,493,501,510,519,528,536],{"type":40,"tag":126,"props":417,"children":418},{"class":128,"line":129},[419],{"type":40,"tag":126,"props":420,"children":421},{},[422],{"type":46,"value":423},"\u003CTarget Name=\"IncludeGeneratedFiles\" BeforeTargets=\"BeforeBuild\">\n",{"type":40,"tag":126,"props":425,"children":426},{"class":128,"line":138},[427],{"type":40,"tag":126,"props":428,"children":429},{},[430],{"type":46,"value":431},"  \n",{"type":40,"tag":126,"props":433,"children":434},{"class":128,"line":147},[435],{"type":40,"tag":126,"props":436,"children":437},{},[438],{"type":46,"value":439},"  \u003C!-- Your logic that generates files goes here -->\n",{"type":40,"tag":126,"props":441,"children":442},{"class":128,"line":156},[443],{"type":40,"tag":126,"props":444,"children":446},{"emptyLinePlaceholder":445},true,[447],{"type":46,"value":448},"\n",{"type":40,"tag":126,"props":450,"children":452},{"class":128,"line":451},5,[453],{"type":40,"tag":126,"props":454,"children":455},{},[456],{"type":46,"value":135},{"type":40,"tag":126,"props":458,"children":460},{"class":128,"line":459},6,[461],{"type":40,"tag":126,"props":462,"children":463},{},[464],{"type":46,"value":465},"    \u003CNone Include=\"$(IntermediateOutputPath)my-generated-file.xyz\" CopyToOutputDirectory=\"PreserveNewest\"\u002F>\n",{"type":40,"tag":126,"props":467,"children":469},{"class":128,"line":468},7,[470],{"type":40,"tag":126,"props":471,"children":472},{},[473],{"type":46,"value":474},"    \n",{"type":40,"tag":126,"props":476,"children":478},{"class":128,"line":477},8,[479],{"type":40,"tag":126,"props":480,"children":481},{},[482],{"type":46,"value":483},"    \u003C!-- Capture all files of a certain type with a glob -->\n",{"type":40,"tag":126,"props":485,"children":487},{"class":128,"line":486},9,[488],{"type":40,"tag":126,"props":489,"children":490},{},[491],{"type":46,"value":492},"    \u003CNone Include=\"$(IntermediateOutputPath)generated\\*.xyz\" CopyToOutputDirectory=\"PreserveNewest\"\u002F>\n",{"type":40,"tag":126,"props":494,"children":496},{"class":128,"line":495},10,[497],{"type":40,"tag":126,"props":498,"children":499},{"emptyLinePlaceholder":445},[500],{"type":46,"value":448},{"type":40,"tag":126,"props":502,"children":504},{"class":128,"line":503},11,[505],{"type":40,"tag":126,"props":506,"children":507},{},[508],{"type":46,"value":509},"    \u003C!-- Register generated files for proper cleanup -->\n",{"type":40,"tag":126,"props":511,"children":513},{"class":128,"line":512},12,[514],{"type":40,"tag":126,"props":515,"children":516},{},[517],{"type":46,"value":518},"    \u003CFileWrites Include=\"$(IntermediateOutputPath)my-generated-file.xyz\" \u002F>\n",{"type":40,"tag":126,"props":520,"children":522},{"class":128,"line":521},13,[523],{"type":40,"tag":126,"props":524,"children":525},{},[526],{"type":46,"value":527},"    \u003CFileWrites Include=\"$(IntermediateOutputPath)generated\\*.xyz\" \u002F>\n",{"type":40,"tag":126,"props":529,"children":531},{"class":128,"line":530},14,[532],{"type":40,"tag":126,"props":533,"children":534},{},[535],{"type":46,"value":162},{"type":40,"tag":126,"props":537,"children":539},{"class":128,"line":538},15,[540],{"type":40,"tag":126,"props":541,"children":542},{},[543],{"type":46,"value":544},"\u003C\u002FTarget>\n",{"type":40,"tag":197,"props":546,"children":548},{"id":547},"for-generated-source-files-code-that-needs-compilation",[549],{"type":46,"value":550},"For Generated Source Files (Code That Needs Compilation)",{"type":40,"tag":56,"props":552,"children":553},{},[554,556,561,563,571,573,578,580,585],{"type":46,"value":555},"If you're generating ",{"type":40,"tag":98,"props":557,"children":559},{"className":558},[],[560],{"type":46,"value":242},{"type":46,"value":562}," files that need to be compiled, use ",{"type":40,"tag":209,"props":564,"children":565},{},[566],{"type":40,"tag":98,"props":567,"children":569},{"className":568},[],[570],{"type":46,"value":173},{"type":46,"value":572},". This is the correct timing for adding ",{"type":40,"tag":98,"props":574,"children":576},{"className":575},[],[577],{"type":46,"value":103},{"type":46,"value":579}," items — it runs late enough that the file generation has occurred, but before the compiler runs. Using ",{"type":40,"tag":98,"props":581,"children":583},{"className":582},[],[584],{"type":46,"value":406},{"type":46,"value":586}," is too early for some scenarios and may not work reliably with all SDK features.",{"type":40,"tag":115,"props":588,"children":590},{"className":117,"code":589,"language":119,"meta":120,"style":120},"\u003CTarget Name=\"IncludeGeneratedSourceFiles\" BeforeTargets=\"CoreCompile;BeforeCompile\">\n  \u003CPropertyGroup>\n    \u003CGeneratedCodeDir>$(IntermediateOutputPath)Generated\\\u003C\u002FGeneratedCodeDir>\n    \u003CGeneratedFilePath>$(GeneratedCodeDir)MyGeneratedFile.cs\u003C\u002FGeneratedFilePath>\n  \u003C\u002FPropertyGroup>\n\n  \u003CMakeDir Directories=\"$(GeneratedCodeDir)\" \u002F>\n\n  \u003C!-- Your logic that generates the .cs file goes here -->\n\n  \u003CItemGroup>\n    \u003CCompile Include=\"$(GeneratedFilePath)\" \u002F>\n    \u003CFileWrites Include=\"$(GeneratedFilePath)\" \u002F>\n  \u003C\u002FItemGroup>\n\u003C\u002FTarget>\n",[591],{"type":40,"tag":98,"props":592,"children":593},{"__ignoreMap":120},[594,602,610,618,626,634,641,649,656,664,671,678,685,692,699],{"type":40,"tag":126,"props":595,"children":596},{"class":128,"line":129},[597],{"type":40,"tag":126,"props":598,"children":599},{},[600],{"type":46,"value":601},"\u003CTarget Name=\"IncludeGeneratedSourceFiles\" BeforeTargets=\"CoreCompile;BeforeCompile\">\n",{"type":40,"tag":126,"props":603,"children":604},{"class":128,"line":138},[605],{"type":40,"tag":126,"props":606,"children":607},{},[608],{"type":46,"value":609},"  \u003CPropertyGroup>\n",{"type":40,"tag":126,"props":611,"children":612},{"class":128,"line":147},[613],{"type":40,"tag":126,"props":614,"children":615},{},[616],{"type":46,"value":617},"    \u003CGeneratedCodeDir>$(IntermediateOutputPath)Generated\\\u003C\u002FGeneratedCodeDir>\n",{"type":40,"tag":126,"props":619,"children":620},{"class":128,"line":156},[621],{"type":40,"tag":126,"props":622,"children":623},{},[624],{"type":46,"value":625},"    \u003CGeneratedFilePath>$(GeneratedCodeDir)MyGeneratedFile.cs\u003C\u002FGeneratedFilePath>\n",{"type":40,"tag":126,"props":627,"children":628},{"class":128,"line":451},[629],{"type":40,"tag":126,"props":630,"children":631},{},[632],{"type":46,"value":633},"  \u003C\u002FPropertyGroup>\n",{"type":40,"tag":126,"props":635,"children":636},{"class":128,"line":459},[637],{"type":40,"tag":126,"props":638,"children":639},{"emptyLinePlaceholder":445},[640],{"type":46,"value":448},{"type":40,"tag":126,"props":642,"children":643},{"class":128,"line":468},[644],{"type":40,"tag":126,"props":645,"children":646},{},[647],{"type":46,"value":648},"  \u003CMakeDir Directories=\"$(GeneratedCodeDir)\" \u002F>\n",{"type":40,"tag":126,"props":650,"children":651},{"class":128,"line":477},[652],{"type":40,"tag":126,"props":653,"children":654},{"emptyLinePlaceholder":445},[655],{"type":46,"value":448},{"type":40,"tag":126,"props":657,"children":658},{"class":128,"line":486},[659],{"type":40,"tag":126,"props":660,"children":661},{},[662],{"type":46,"value":663},"  \u003C!-- Your logic that generates the .cs file goes here -->\n",{"type":40,"tag":126,"props":665,"children":666},{"class":128,"line":495},[667],{"type":40,"tag":126,"props":668,"children":669},{"emptyLinePlaceholder":445},[670],{"type":46,"value":448},{"type":40,"tag":126,"props":672,"children":673},{"class":128,"line":503},[674],{"type":40,"tag":126,"props":675,"children":676},{},[677],{"type":46,"value":135},{"type":40,"tag":126,"props":679,"children":680},{"class":128,"line":512},[681],{"type":40,"tag":126,"props":682,"children":683},{},[684],{"type":46,"value":144},{"type":40,"tag":126,"props":686,"children":687},{"class":128,"line":521},[688],{"type":40,"tag":126,"props":689,"children":690},{},[691],{"type":46,"value":153},{"type":40,"tag":126,"props":693,"children":694},{"class":128,"line":530},[695],{"type":40,"tag":126,"props":696,"children":697},{},[698],{"type":46,"value":162},{"type":40,"tag":126,"props":700,"children":701},{"class":128,"line":538},[702],{"type":40,"tag":126,"props":703,"children":704},{},[705],{"type":46,"value":544},{"type":40,"tag":56,"props":707,"children":708},{},[709,711,717,718,724],{"type":46,"value":710},"Note: Specifying both ",{"type":40,"tag":98,"props":712,"children":714},{"className":713},[],[715],{"type":46,"value":716},"CoreCompile",{"type":46,"value":105},{"type":40,"tag":98,"props":719,"children":721},{"className":720},[],[722],{"type":46,"value":723},"BeforeCompile",{"type":46,"value":725}," ensures the target runs before whichever target comes first, providing robust ordering regardless of customizations in the build.",{"type":40,"tag":49,"props":727,"children":729},{"id":728},"target-timing",[730],{"type":46,"value":731},"Target Timing",{"type":40,"tag":56,"props":733,"children":734},{},[735,737,743],{"type":46,"value":736},"Choose the ",{"type":40,"tag":98,"props":738,"children":740},{"className":739},[],[741],{"type":46,"value":742},"BeforeTargets",{"type":46,"value":744}," value based on the type of file being generated:",{"type":40,"tag":62,"props":746,"children":747},{},[748,775,795],{"type":40,"tag":66,"props":749,"children":750},{},[751,760,762,767,768,773],{"type":40,"tag":209,"props":752,"children":753},{},[754],{"type":40,"tag":98,"props":755,"children":757},{"className":756},[],[758],{"type":46,"value":759},"BeforeTargets=\"BeforeBuild\"",{"type":46,"value":761}," — For non-code files added to ",{"type":40,"tag":98,"props":763,"children":765},{"className":764},[],[766],{"type":46,"value":398},{"type":46,"value":392},{"type":40,"tag":98,"props":769,"children":771},{"className":770},[],[772],{"type":46,"value":390},{"type":46,"value":774},". Runs early enough for copy-to-output scenarios.",{"type":40,"tag":66,"props":776,"children":777},{},[778,786,788,793],{"type":40,"tag":209,"props":779,"children":780},{},[781],{"type":40,"tag":98,"props":782,"children":784},{"className":783},[],[785],{"type":46,"value":173},{"type":46,"value":787}," — For generated source files added to ",{"type":40,"tag":98,"props":789,"children":791},{"className":790},[],[792],{"type":46,"value":103},{"type":46,"value":794},". Ensures the file is included before the compiler runs.",{"type":40,"tag":66,"props":796,"children":797},{},[798,807,809,814,815,820,822,827],{"type":40,"tag":209,"props":799,"children":800},{},[801],{"type":40,"tag":98,"props":802,"children":804},{"className":803},[],[805],{"type":46,"value":806},"BeforeTargets=\"AssignTargetPaths\"",{"type":46,"value":808}," — The \"final stop\" before ",{"type":40,"tag":98,"props":810,"children":812},{"className":811},[],[813],{"type":46,"value":398},{"type":46,"value":105},{"type":40,"tag":98,"props":816,"children":818},{"className":817},[],[819],{"type":46,"value":390},{"type":46,"value":821}," items (among others) are transformed into new items. Use as a fallback if ",{"type":40,"tag":98,"props":823,"children":825},{"className":824},[],[826],{"type":46,"value":406},{"type":46,"value":828}," is too early.",{"type":40,"tag":49,"props":830,"children":832},{"id":831},"globbing-behavior",[833],{"type":46,"value":834},"Globbing Behavior",{"type":40,"tag":56,"props":836,"children":837},{},[838,840,845],{"type":46,"value":839},"Globs behave according to ",{"type":40,"tag":209,"props":841,"children":842},{},[843],{"type":46,"value":844},"when",{"type":46,"value":846}," the glob took place:",{"type":40,"tag":848,"props":849,"children":850},"table",{},[851,870],{"type":40,"tag":852,"props":853,"children":854},"thead",{},[855],{"type":40,"tag":856,"props":857,"children":858},"tr",{},[859,865],{"type":40,"tag":860,"props":861,"children":862},"th",{},[863],{"type":46,"value":864},"Glob Location",{"type":40,"tag":860,"props":866,"children":867},{},[868],{"type":46,"value":869},"Files Captured",{"type":40,"tag":871,"props":872,"children":873},"tbody",{},[874,888],{"type":40,"tag":856,"props":875,"children":876},{},[877,883],{"type":40,"tag":878,"props":879,"children":880},"td",{},[881],{"type":46,"value":882},"Outside of a target",{"type":40,"tag":878,"props":884,"children":885},{},[886],{"type":46,"value":887},"Only files visible during Evaluation phase (before build starts)",{"type":40,"tag":856,"props":889,"children":890},{},[891,896],{"type":40,"tag":878,"props":892,"children":893},{},[894],{"type":46,"value":895},"Inside of a target",{"type":40,"tag":878,"props":897,"children":898},{},[899],{"type":46,"value":900},"Files visible when the target runs (can capture generated files if timed correctly)",{"type":40,"tag":56,"props":902,"children":903},{},[904,906,912,914,920],{"type":46,"value":905},"This is why the solution places the ",{"type":40,"tag":98,"props":907,"children":909},{"className":908},[],[910],{"type":46,"value":911},"\u003CItemGroup>",{"type":46,"value":913}," inside a ",{"type":40,"tag":98,"props":915,"children":917},{"className":916},[],[918],{"type":46,"value":919},"\u003CTarget>",{"type":46,"value":921}," - the glob runs during execution when the generated files exist.",{"type":40,"tag":49,"props":923,"children":925},{"id":924},"relevant-links",[926],{"type":46,"value":927},"Relevant Links",{"type":40,"tag":62,"props":929,"children":930},{},[931,939,948,957,967,977],{"type":40,"tag":66,"props":932,"children":933},{},[934],{"type":40,"tag":186,"props":935,"children":937},{"href":188,"rel":936},[190],[938],{"type":46,"value":193},{"type":40,"tag":66,"props":940,"children":941},{},[942],{"type":40,"tag":186,"props":943,"children":946},{"href":944,"rel":945},"https:\u002F\u002Fdocs.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fbuild-process-overview#evaluation-phase",[190],[947],{"type":46,"value":202},{"type":40,"tag":66,"props":949,"children":950},{},[951],{"type":40,"tag":186,"props":952,"children":955},{"href":953,"rel":954},"https:\u002F\u002Fdocs.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fbuild-process-overview#execution-phase",[190],[956],{"type":46,"value":221},{"type":40,"tag":66,"props":958,"children":959},{},[960],{"type":40,"tag":186,"props":961,"children":964},{"href":962,"rel":963},"https:\u002F\u002Fdocs.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fcommon-msbuild-project-items",[190],[965],{"type":46,"value":966},"Common Item Types",{"type":40,"tag":66,"props":968,"children":969},{},[970],{"type":40,"tag":186,"props":971,"children":974},{"href":972,"rel":973},"https:\u002F\u002Fgithub.com\u002Fdotnet\u002Fsdk\u002Fblob\u002Fmain\u002Fsrc\u002FTasks\u002FMicrosoft.NET.Build.Tasks\u002Ftargets\u002FMicrosoft.NET.Sdk.DefaultItems.props",[190],[975],{"type":46,"value":976},"How the SDK imports items by default",{"type":40,"tag":66,"props":978,"children":979},{},[980],{"type":40,"tag":186,"props":981,"children":984},{"href":982,"rel":983},"https:\u002F\u002Flearn.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fcustomize-your-build#handle-generated-files",[190],[985],{"type":46,"value":986},"Official docs: Handle generated files",{"type":40,"tag":988,"props":989,"children":990},"style",{},[991],{"type":46,"value":992},"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":994,"total":1099},[995,1010,1025,1043,1057,1077,1087],{"slug":996,"name":996,"fn":997,"description":998,"org":999,"tags":1000,"stars":22,"repoUrl":23,"updatedAt":1009},"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},[1001,1002,1005,1006],{"name":17,"slug":18,"type":15},{"name":1003,"slug":1004,"type":15},"Code Analysis","code-analysis",{"name":20,"slug":21,"type":15},{"name":1007,"slug":1008,"type":15},"Performance","performance","2026-07-12T08:23:25.400375",{"slug":1011,"name":1011,"fn":1012,"description":1013,"org":1014,"tags":1015,"stars":22,"repoUrl":23,"updatedAt":1024},"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},[1016,1017,1020,1021],{"name":17,"slug":18,"type":15},{"name":1018,"slug":1019,"type":15},"Android","android",{"name":20,"slug":21,"type":15},{"name":1022,"slug":1023,"type":15},"Microsoft","microsoft","2026-07-12T08:23:21.595572",{"slug":1026,"name":1026,"fn":1027,"description":1028,"org":1029,"tags":1030,"stars":22,"repoUrl":23,"updatedAt":1042},"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},[1031,1032,1033,1036,1039],{"name":17,"slug":18,"type":15},{"name":20,"slug":21,"type":15},{"name":1034,"slug":1035,"type":15},"iOS","ios",{"name":1037,"slug":1038,"type":15},"macOS","macos",{"name":1040,"slug":1041,"type":15},"Observability","observability","2026-07-12T08:23:20.369986",{"slug":1044,"name":1044,"fn":1045,"description":1046,"org":1047,"tags":1048,"stars":22,"repoUrl":23,"updatedAt":1056},"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},[1049,1050,1053],{"name":1003,"slug":1004,"type":15},{"name":1051,"slug":1052,"type":15},"QA","qa",{"name":1054,"slug":1055,"type":15},"Testing","testing","2026-07-12T08:23:51.277743",{"slug":1058,"name":1058,"fn":1059,"description":1060,"org":1061,"tags":1062,"stars":22,"repoUrl":23,"updatedAt":1076},"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},[1063,1064,1067,1070,1073],{"name":17,"slug":18,"type":15},{"name":1065,"slug":1066,"type":15},"Blazor","blazor",{"name":1068,"slug":1069,"type":15},"C#","csharp",{"name":1071,"slug":1072,"type":15},"UI Components","ui-components",{"name":1074,"slug":1075,"type":15},"Web Development","web-development","2026-07-15T06:03:29.216359",{"slug":1078,"name":1078,"fn":1079,"description":1080,"org":1081,"tags":1082,"stars":22,"repoUrl":23,"updatedAt":1086},"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},[1083,1084,1085],{"name":1003,"slug":1004,"type":15},{"name":20,"slug":21,"type":15},{"name":1022,"slug":1023,"type":15},"2026-07-12T08:21:34.637923",{"slug":1088,"name":1088,"fn":1089,"description":1090,"org":1091,"tags":1092,"stars":22,"repoUrl":23,"updatedAt":1098},"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},[1093,1094,1095],{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},{"name":1096,"slug":1097,"type":15},"Engineering","engineering","2026-07-19T05:38:19.340791",96,{"items":1101,"total":1206},[1102,1114,1121,1128,1136,1142,1150,1156,1162,1172,1185,1196],{"slug":1103,"name":1103,"fn":1104,"description":1105,"org":1106,"tags":1107,"stars":1111,"repoUrl":1112,"updatedAt":1113},"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},[1108,1109,1110],{"name":17,"slug":18,"type":15},{"name":1096,"slug":1097,"type":15},{"name":1007,"slug":1008,"type":15},5535,"https:\u002F\u002Fgithub.com\u002Fdotnet\u002Fmsbuild","2026-07-22T05:37:33.965588",{"slug":996,"name":996,"fn":997,"description":998,"org":1115,"tags":1116,"stars":22,"repoUrl":23,"updatedAt":1009},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1117,1118,1119,1120],{"name":17,"slug":18,"type":15},{"name":1003,"slug":1004,"type":15},{"name":20,"slug":21,"type":15},{"name":1007,"slug":1008,"type":15},{"slug":1011,"name":1011,"fn":1012,"description":1013,"org":1122,"tags":1123,"stars":22,"repoUrl":23,"updatedAt":1024},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1124,1125,1126,1127],{"name":17,"slug":18,"type":15},{"name":1018,"slug":1019,"type":15},{"name":20,"slug":21,"type":15},{"name":1022,"slug":1023,"type":15},{"slug":1026,"name":1026,"fn":1027,"description":1028,"org":1129,"tags":1130,"stars":22,"repoUrl":23,"updatedAt":1042},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1131,1132,1133,1134,1135],{"name":17,"slug":18,"type":15},{"name":20,"slug":21,"type":15},{"name":1034,"slug":1035,"type":15},{"name":1037,"slug":1038,"type":15},{"name":1040,"slug":1041,"type":15},{"slug":1044,"name":1044,"fn":1045,"description":1046,"org":1137,"tags":1138,"stars":22,"repoUrl":23,"updatedAt":1056},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1139,1140,1141],{"name":1003,"slug":1004,"type":15},{"name":1051,"slug":1052,"type":15},{"name":1054,"slug":1055,"type":15},{"slug":1058,"name":1058,"fn":1059,"description":1060,"org":1143,"tags":1144,"stars":22,"repoUrl":23,"updatedAt":1076},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1145,1146,1147,1148,1149],{"name":17,"slug":18,"type":15},{"name":1065,"slug":1066,"type":15},{"name":1068,"slug":1069,"type":15},{"name":1071,"slug":1072,"type":15},{"name":1074,"slug":1075,"type":15},{"slug":1078,"name":1078,"fn":1079,"description":1080,"org":1151,"tags":1152,"stars":22,"repoUrl":23,"updatedAt":1086},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1153,1154,1155],{"name":1003,"slug":1004,"type":15},{"name":20,"slug":21,"type":15},{"name":1022,"slug":1023,"type":15},{"slug":1088,"name":1088,"fn":1089,"description":1090,"org":1157,"tags":1158,"stars":22,"repoUrl":23,"updatedAt":1098},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1159,1160,1161],{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},{"name":1096,"slug":1097,"type":15},{"slug":1163,"name":1163,"fn":1164,"description":1165,"org":1166,"tags":1167,"stars":22,"repoUrl":23,"updatedAt":1171},"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},[1168,1169,1170],{"name":17,"slug":18,"type":15},{"name":1096,"slug":1097,"type":15},{"name":1007,"slug":1008,"type":15},"2026-07-19T05:38:18.364937",{"slug":1173,"name":1173,"fn":1174,"description":1175,"org":1176,"tags":1177,"stars":22,"repoUrl":23,"updatedAt":1184},"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},[1178,1179,1182,1183],{"name":1096,"slug":1097,"type":15},{"name":1180,"slug":1181,"type":15},"Monitoring","monitoring",{"name":1007,"slug":1008,"type":15},{"name":1054,"slug":1055,"type":15},"2026-07-12T08:21:35.865649",{"slug":1186,"name":1186,"fn":1187,"description":1188,"org":1189,"tags":1190,"stars":22,"repoUrl":23,"updatedAt":1195},"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},[1191,1192,1193,1194],{"name":17,"slug":18,"type":15},{"name":20,"slug":21,"type":15},{"name":1096,"slug":1097,"type":15},{"name":1007,"slug":1008,"type":15},"2026-07-12T08:21:40.961722",{"slug":1197,"name":1197,"fn":1198,"description":1199,"org":1200,"tags":1201,"stars":22,"repoUrl":23,"updatedAt":1205},"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},[1202,1203,1204],{"name":20,"slug":21,"type":15},{"name":1096,"slug":1097,"type":15},{"name":1051,"slug":1052,"type":15},"2026-07-19T05:38:14.336279",144]