dotnet-msbuild-execution

Attach a custom target with BeforeTargets or AfterTargets naming an SDK target such as Build or CoreCompile, or append to a DependsOn property like CompileDependsOn in Directory.Build.targets. Defining a target named AfterBuild in a project file silently loses to the SDK's empty target.

Declare Inputs and Outputs on the target so MSBuild skips it when every output is at least as new as its inputs. Targets without Outputs run every build, and register-only targets should Touch a marker file and add it to FileWrites.

The implicit Sdk.targets import defines empty BeforeBuild and AfterBuild targets after the project body, so a same-named target in the project file loses silently. Use a uniquely named target with AfterTargets="Build" instead.

Globs outside a target expand during evaluation and cannot see files written later, so the generating target must add the file to an item type like None with CopyToOutputDirectory metadata. Hook before AssignTargetPaths, the last target that assigns TargetPath.

DependsOnTargets runs the named target in the caller's scope so properties and items it sets remain visible. CallTarget runs in a new scope and only TargetOutputs come back, while properties and items it sets stay invisible to the caller.

A target attached to Build runs in the outer build and in every inner build dispatched per TargetFrameworks entry. Gate per-assembly work with '$(TargetFramework)' != '' or outer-build work with '$(IsCrossTargetingBuild)' == 'true'.