including-generated-files

MSBuild ignores generated files because evaluation-time globs execute before custom build tasks run. Adding generated paths to Compile and FileWrites inside a target with BeforeTargets timing using $(IntermediateOutputPath) fixes compilation gaps.

To include generated .cs files in MSBuild compilation, add them to the Compile item group inside a target with BeforeTargets="CoreCompile;BeforeCompile" timing so later targets see the files after generation.

To ensure MSBuild Clean removes build-generated files, add generated paths into the FileWrites item group inside your target. This registers them with cleanup so intermediate output files are deleted during Clean.

Yes, you can use BeforeTargets to fix missing generated types in .NET builds. Setting BeforeTargets="CoreCompile;BeforeCompile" ensures generated source files are added to Compile before the compiler executes.

The correct path for generated files in MSBuild custom targets is $(IntermediateOutputPath). Using this variable avoids incorrect directories and ensures later compilation targets locate the generated source and content files reliably.

Yes, generated non-code artifacts must be added to None or Content in MSBuild for copying to output directories. They should also be added to FileWrites so the Clean target removes them properly.