You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In other build systems, we can access the list of tracked variable in a given context and use it for simple debugging. e.g. CMake provides get_cmake_property(allVars VARIABLES), that sets CMake's internal dictionary tracking properties in user variable allVars, which can then be iterated for printing key/values etc.
With MSBuild, we can either use VS for high quality script debugging (of XML files), or we can use plain dumps /v:d[iag], binary log etc. However, I am looking for a more granular control over internal dictionary, which MSBuild uses to track properties' names and current values in the context. Something like:
<TargetName="MyTarget">
<!-- while running MyTarget in a very large/complex project, print/dump list/snapshot of *all* properties known to MSBuild at this point (all props include: built-ins, environment vars, custom properties) -->
<ErrorMessage="dumping all props in simple (later-diffable) output:%(MSBuildPropertiesDictionary.Identity): %(MSBuildPropertiesDictionary.Value)" />
In other build systems, we can access the list of tracked variable in a given context and use it for simple debugging. e.g. CMake provides
get_cmake_property(allVars VARIABLES)
, that sets CMake's internal dictionary tracking properties in user variableallVars
, which can then be iterated for printing key/values etc.With MSBuild, we can either use VS for high quality script debugging (of XML files), or we can use plain dumps
/v:d[iag]
, binary log etc. However, I am looking for a more granular control over internal dictionary, which MSBuild uses to track properties' names and current values in the context. Something like:similar discussions:
The text was updated successfully, but these errors were encountered: