Tweet Series on Visual Studio CodeLens [11-20]


 

Here are tweets 11-20.

Tweet #11 : #VisualStudio #CodeLens Test Indicators helps identify and run unit tests which test the current code element.

Embedded image permalink

 

Tweet #12 : #VisualStudio #CodeLens details has an icon next to each change. The icon shows where the change came from.

Embedded image permalink

 

Tweet #13 : #VisualStudio #CodeLens allows you to visualize references on a CodeMap.

Embedded image permalink

 

Tweet #14 : #VisualStudio #CodeLens processing in Team Foundation Server can be managed using TFSConfig CodeIndex command - http://msdn.microsoft.com/en-us/library/dn280925.aspx …

 

Tweet #15 :  #VisualStudio #CodeLens color & font can be changed from Tools, Options, Environment, Fonts and Colors.

Embedded image permalink

 

Tweet #16 : You can preview the referencing code from #VisualStudio #CodeLens by moving your mouse over any reference.

Embedded image permalink

 

Tweet #17 : #Visual Studio #CodeLens has been integrated with Code Map to navigate the diagnostics data in exceptions. http://blogs.msdn.com/b/visualstudioalm/archive/2014/03/07/enhancements-to-debugging-exceptions-with-intellitrace-in-visual-studio-2013.aspx …

 

Tweet #18 : You can find when a code element was last changed in #VisualStudio #CodeLens Authors Indicator.

Embedded image permalink

 

Tweet #19 : Steven Lange wrote this great article talking about the value of #VisualStudio #CodeLens - http://blogs.msdn.com/b/slange/archive/2014/06/17/panels-vs-context-a-tale-of-two-visual-studios-and-a-practical-explanation-of-the-value-of-codelens.aspx …

Tweet #20 : #VisualStudio #CodeLens Changes indicator shows if you have an old version of code element/file-See +1 below.

Embedded image permalink

 

Tweets 1-10 are listed here.

Comments (0)

Skip to main content