How to filter for my custom project? about concordextensibilitysamples HOT 1 OPEN

Hi,
I agree, before it was easy to have custom visualizers bound to one solution: you just needed to put your .natvis in one of your project, along with the .dll, whose path could be given in <DisplayString LegacyAddin=...>.
This way, every developer that downloaded your project could benefit from the visualizer without even knowing he was using a custom visualizer.

Now, with extensions, you must explain them why what they you use to see in debug does not work anymore, and that they must install an extension to have it back. Back to the same pain as when natvis files had to be installed in main %VSINSTALLDIR%\Common7\Packages\Debugger\Visualizers.

Turning custom visualizers into extensions is very neat and consistent, but it would be just perfect to be able to supply them along with projects or solution too, for example by copying the .vsdconfig and the .dll in the same directory as the .natvis (since no path can be given anymore, now that LegacyAddin disappeared)

from concordextensibilitysamples.