domains / families / devops / including-generated-files

including-generated-files

separate

Own MSBuild generated-artifact integration. USE FOR: a target that creates or should create source, Content, None, or another physical file but the artifact is missing from compilation or output; target timing; evaluation-time glob misses; $(IntermediateOutputPath) placement; and FileWrites clean tracking. The prompt may describe the generated artifact without naming the producing task. DO NOT USE when the primary defect is general Include/Remove/Update semantics, item metadata or batching, duplicate/overlapping declarations, or a generated-item identity relationship; use item-management. Exclude Roslyn source-generator internals and non-MSBuild systems.

When to use

• target that creates source, Content, None, or another physical file
• artifact missing from compilation or output
• target timing
• evaluation-time glob misses
• $(IntermediateOutputPath) placement
• FileWrites clean tracking

When not to use

• general Include/Remove/Update semantics
• item metadata or batching
• duplicate/overlapping declarations
• generated-item identity relationship
• Roslyn source-generator internals
• non-MSBuild systems

Skill page

Source