In my previous post I’ve been critic on the Visual Studio 11 Beta greyed UI (and especially greyed icons!!). Let’s be positive, and frankly it is easy to be positive. I am using VS 11 beta for a week and it will be an awesome release in terms of features and performance improvement. My only hope is that they won’t waste all these efforts, and they’ll fix the depressing UI theme, or at least let the choice to the user to get back colors where it makes the most sense (icons, panels boundaries…).
So one apparently hidden feature, I discovered through the John Robbin’s blog is the new diffing capabilities of VS11! Just type in a command window…
C:\Program Files\Microsoft Visual Studio 11.0\Common7\IDE>devenv /diff C:\Tests\OnNUnit_Src\NUnit2_5_3\src\NUnitCore\core\TestMethod.cs C:\Tests\OnNUnit_Src\NUnit2_5_8\src\NUnitCore\core\TestMethod.cs…and you’re done!
If a VS11 instance exists, it will be used, else, a new VS11 instance will be started to host the comparison panel. And there will be also the possibility to compare folders. Notes that with a bit more work, the VS11 diff text files feature could look like the awesome Kompare UI:
And, let’s precise a cool side note, the current version of NDepend supports already this VS11 feature! In the file VisualNDependOptions.xml, that you can find in the folder specified in NDepend > Options > Export/Import/Reset Options, you just need to refactor the <DiffTool/> tag this way…
<DiffTool ExeFilePath=”C:\Program Files\Microsoft Visual Studio 11.0\Common7\IDE\devenv.exe” CommandLineArgs=” /diff $OldSrcFilePath$ $NewSrcFilePath$” />… and it just works. Of course the next version of NDepend will integrate in VS11 and will cleanly supports this feature:
The user won’t have to tweak the XML manually, VS11 diff will be proposed per default in the list of default diff tools that the user can plug to NDepend:



