Target when project AssemblyAttribute AssemblyInfo is generated

[mwpowellhtx]

When are the AssemblyInfo.cs attributes generated in response to CSPROJ level <AssemblyAttribute/> items? Anyone have any ideas?

Using msbuild --targets:targets.txt to try to glean that for the project(s) in question, I get the following output, just for instance. But I do not see anything that jumps out as an AssemblyInfo target, per se.

Also, I assume these are listed in order of execution.

Thank you...

ApplyPackageManagement
ApplyPackageManagementItems
BeforePackageManagement
AfterPackageManagement
_GetRequiredWorkloads
ResolvePackageDependenciesDesignTime
CollectSDKReferencesDesignTime
CollectResolvedSDKReferencesDesignTime
ResolveFrameworkReferences
ResolveProjectReferencesDesignTime2
ResolveFrameworkReferencesDesignTime
CollectPackageReferences
CollectSuggestedWorkloads
_CheckCompileDesignTimePrerequisite
CollectAnalyzersDesignTime
CollectResolvedCompilationReferencesDesignTime
CollectUpToDateCheckInputDesignTime
CollectUpToDateCheckOutputDesignTime
CollectUpToDateCheckBuiltDesignTime
CompileDesignTime
ComputeXamarinTargetFrameworks
GetTargetFrameworks
_ComputeTargetFrameworkItems
GetTargetFrameworksWithPlatformFromInnerBuilds
DispatchToInnerBuilds
Build
_SetBuildInnerTarget
Clean
Rebuild
Restore
GenerateRestoreGraphFile
CollectCentralPackageVersions
CollectPackageDownloads
CollectFrameworkReferences
_LoadRestoreGraphEntryPoints
_FilterRestoreGraphProjectInputItems
_GenerateRestoreGraph
_GenerateRestoreGraphProjectEntry
_GenerateRestoreSpecs
_GenerateDotnetCliToolReferenceSpecs
_GetProjectJsonPath
_GetRestoreProjectStyle
EnableIntermediateOutputPathMismatchWarning
_GetRestoreTargetFrameworksOutput
_GetRestoreTargetFrameworksAsItems
_GetRestoreSettings
_GetRestoreSettingsCurrentProject
_GetRestoreSettingsAllFrameworks
_GetRestoreSettingsPerFramework
_GenerateRestoreProjectSpec
_GenerateProjectRestoreGraph
_GenerateRestoreDependencies
_GenerateProjectRestoreGraphAllFrameworks
_GenerateProjectRestoreGraphCurrentProject
_GenerateProjectRestoreGraphPerFramework
_GenerateRestoreProjectPathItemsCurrentProject
_GenerateRestoreProjectPathItemsPerFramework
_GenerateRestoreProjectPathItems
_GenerateRestoreProjectPathItemsAllFrameworks
_GenerateRestoreProjectPathWalk
_GetAllRestoreProjectPathItems
_GetRestoreSettingsOverrides
_GetRestorePackagesPathOverride
_GetRestoreRepositoryPathOverride
_GetRestoreSourcesOverride
_GetRestoreFallbackFoldersOverride
_Is

[baronfel]

Check out the GenerateAssemblyInfo target in the dotnet/sdk repo. This particular functionality is provided by the SDK itself, not MSBuild.

[mwpowellhtx]

Huh that is interesting. I wonder why that does not appear in the listed targets? Assuming targets are reported as they are seen during the natural build pipeline.

[baronfel]

That's a good question indeed. Have you tried taking an MSBuild Binary Log and checked the targets run in the viewer? That would be the most complete picture of what's going on.

[mwpowellhtx]

Indeed I have not; that's a bit more in depth of a report than I would like for the detail I am aiming for there, I think. But I may look into it after all. Thanks.

[rainersigwald]

Also, I assume these are listed in order of execution.

They are not; in the general case there's no way to predict the execution order from an evaluated project. Looking at a build log shows you what projects did run and in what order, and is the only way to really know that.

[rainersigwald]

Because of design decisions very early in MSBuild's lifetime, the order of targets is dynamically determined during the build. The detailed rules are described in the doc Target Build Order. Because of that dynamism, there's no way to sort the list of targets.

[mwpowellhtx]

Okay, but does that invalidate the question, i.e. to LOG what was encountered at the time it was encountered (?). I cannot speak for others, but I think, objectively, that is what anyone has been asking about, for a long, long time.

[rainersigwald]

I don't understand what you're asking. The standard build log can log all targets that are executed, in order, at higher verbosities.

[mwpowellhtx]

The question is, the targets only; don't care about the verbosity, that is way TMI.

[baronfel]

The --targets switch only prints the 'entry target' list because it only prints what happens through project evaluation, not target execution. If you'd like to trace what targets are actually visited during building specific target(s), that's a valid request. Thankfully it's fairly simple to do so yourself, if you'd like to see how useful it might be to you. It should be a matter of writing a small custom logger that logs based off of the TargetStarted event handler on an IEventSource, and then you're all set.