Currently in VS2017 the only way that I found to get Native code metrics, is to build a C++ Unit test with the Native Unittest framwork. After you created just the tiniest of unit test, you can run the "Analyse code coverage" test. That one - and that one only ! - will give you the code metrics for native code.
Of course we want the code metrics without a unit test also, and for ALL the code!
I'm normally relying on the offline help when working at a customer site where I do not get any internet connection. Please at least re-instate the offline help from VS2015 in the VS2017 version. If not as a standard option, then as a VS extension!!!
82 votesunder review · 3 comments · Visual Studio IDE » Languages - C++ · Flag idea as inappropriate… · Admin →
This would seriously reduce the amount of typing work in C++ as in comparison to C#!
I'm not lazy, but it is one of the repeatedly heared complaints of C# programmers, if they have to do work in C++.
We are currently evaluating how we can enhance the support for C++ Code Maps. We will be providing an update soon.
914 votesunder review · 4 comments · Visual Studio IDE » Languages - C++ · Flag idea as inappropriate… · Admin →
193 votesunder review · 13 comments · Visual Studio IDE » Languages - C++ · Flag idea as inappropriate… · Admin →
MFC is still widely used in many legacy and even new desktop applications. It's about the only real way to build quickly reactive components integrated with the MS-Windows API.
Please, please put the source - and the missing parts and build scripts - in open source and it will fly from there.......
We (the community) will expand it from there......