<div dir="ltr">FWIW I actually wrote one that's used for anyone working on Chromium. It's a Visual Studio plugin, and unfortunately you need a fairly significant amount of plumbing to get it up and running, but once it's there it's not too bad to add new stuff to. You still wouldn't want to do it for every little thing, as for simpler cases natvis is still superior. But it does give you quite a bit more control over how things are displayed. If you're interested, the project is here:<div>
<br></div><div><a href="https://github.com/chromium/vs-chromium/">https://github.com/chromium/vs-chromium/</a><br></div><div><br></div><div>and the stuff of interest, after you cut through all the boilerplate, is in here: <a href="https://github.com/chromium/vs-chromium/tree/master/src/DkmIntegration">https://github.com/chromium/vs-chromium/tree/master/src/DkmIntegration</a></div>
<div><br></div><div>I've thought about doing the same type of thing here, but just getting through all the boiler plate stuff to a simple visualizer up would be a day or two.</div></div><div class="gmail_extra"><br><br>
<div class="gmail_quote">On Thu, Jun 26, 2014 at 2:08 PM, Aaron Ballman <span dir="ltr"><<a href="mailto:aaron.ballman@gmail.com" target="_blank">aaron.ballman@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">On Thu, Jun 26, 2014 at 5:04 PM, Zachary Turner <<a href="mailto:zturner@google.com">zturner@google.com</a>> wrote:<br>
> Looks like we crossed paths. I just submitted an update to this at this<br>
> very moment, although I changed the title of the review. Either way,<br>
> visualizers aren't too critical so if I'll just push it in sometime later<br>
> today. If you have any feedback though let me know as I'm still learning<br>
> this natvis stuff.<br>
><br>
> BTW, do you think there would be any interest in having a DLL where we could<br>
> write arbitrary code to generate the visualization tree? It seems like<br>
> natvis is frustratingly limited in what you can specify.<br>
<br>
</div>It's crossed my mind that this might be a good way to do it, but I<br>
don't honestly know what the cost/benefit ratio would be. I've not<br>
looked into it particularly far, and mostly just lived with natvis<br>
(which is far better than the previous incarnation of debug viewers,<br>
despite all of the & and < problems).<br>
<span class="HOEnZb"><font color="#888888"><br>
~Aaron<br>
</font></span></blockquote></div><br></div>