CCM
-
I often use CCM[^] to find bad code, but had to use it in VS2012 (the most recent supported version). Today I simply downloaded the source and compiled it, and then created a modified Addin file for VS2013 (based on the one for VS2012) and put the files in the Addin directory for VS2013. It works! Yay!
Getting information off the Internet is like taking a drink from a fire hydrant. - Mitchell Kapor
-
I often use CCM[^] to find bad code, but had to use it in VS2012 (the most recent supported version). Today I simply downloaded the source and compiled it, and then created a modified Addin file for VS2013 (based on the one for VS2012) and put the files in the Addin directory for VS2013. It works! Yay!
Getting information off the Internet is like taking a drink from a fire hydrant. - Mitchell Kapor
-
Not sure what version of VS2013 you are using, but under the Analyze menu, you can select "Calculate Code Metrics for Project/Solution" which displays the cyclomatic complexity and other metrics. VS Ultimate has had that feature at least since VS2010.
I am using VS2013 Premium.
Getting information off the Internet is like taking a drink from a fire hydrant. - Mitchell Kapor
-
I often use CCM[^] to find bad code, but had to use it in VS2012 (the most recent supported version). Today I simply downloaded the source and compiled it, and then created a modified Addin file for VS2013 (based on the one for VS2012) and put the files in the Addin directory for VS2013. It works! Yay!
Getting information off the Internet is like taking a drink from a fire hydrant. - Mitchell Kapor
You can also try Line Counter - Writing a Visual Studio 2005 & 2008 Add-In[^]. According to the comments, it can work for VS2012 and higher. In the past, I've used the stand-alone app SourceMonitor[^]