Hello and thank you for the suggestion. We plan to eventually support CodeLens for C++. How that will work remains under discussion, as there are some performance implications to consider, particularly for the “Find All References” aspect of the feature. Since we require running candidates through the IntelliSense compiler to successfully validate references, C++ code by its nature is more tricky and slower to build than .NET code, and the existing CodeLens experience requires all this to work in real-time on multiple functions at once, it’s something we need to be careful with.
We will keep you posted once we have a more definitive plan. Thank you for helping us build a better Visual Studio!
80 votesAnonymous commented
I would benefit from this too. What I would like is to have ability to write library code that understands and uses VS to its fullest extent, including bundling with the library appropriate natvis and natstepfilter files to smooth out debugging experience for users who also use VS as IDE.
As VS2015 has sailed away and VS 2017 is already shipped we probably will have to wait longer but it shouldn't be such a difficult feature to implement.