Previously, I posted about the new XML-style debugger visualizers I discovered in Visual Studio 11. I mentioned that one of reasons the feature has been redesigned is to enable debugging of the visualizers templates defined in default or user-defined
.natvis files. So, it looks there is something more to discover: how to actually make use of the diagnostics capability.
Unfortunately, it seems the new debugger visualizers have not been documented anywhere. At the time of writing this blog, Google reports one link about defaultvis.natvis, it is the brief post on Visual C++ forum.
Luckily, there is a short manual included as comment in header of the
%ProgramFiles%\Microsoft Visual Studio 11.0\Common7\Packages\Debugger\Visualizers\defaultvis.natvis file. It says:
1) give better diagnostic reporting. a) Set the name-value entry under the Debugger registry key: EnableNatvisDiagnostics which is a REG_DWORD to a value of 1 this will output each expression string that is evaluated under the native visualizer into the output window and is good for debugging type definition typos in .natvis files.
The first thing is to figure out where to set the
EnableNatvisDiagnostics flag. The Visual Studio 11 installer does not put it into the registry. Also, there are several
Debugger keys. However, a few experiments proved the flag should be set under
Once it is set, every time Visual Studio 11 debugger is launched and use of visualized types is determined, the .natvis files are parsed and evaluated templates validated. The process is reported in the Output window:
If anything goes wrong, a type definition template is incorrect and its evaluation fails, it is also reported in the Output window:
It will be a very useful feature especially when defining visualizers of complex types. Previous versions of Visual Studio used old format of templates defined in autoexp.dat file which stated its own DSL based on regular expressions, so the syntax was complex and fragile, and as Andy Pennel has confessed, not documented. (Here kudos to Avery Lee who did great job reverse-engineering the autoexp.dat syntax.)
At least, this time folks get the XML Schema for the Visual Studio debugger visualizers.