Note that WinDBG can be integrated into Visual Studio (since VS2012). See http://blogs.msdn.com/b/mariohewa...-2012-and-windbg-integration.aspx
There is a ton of stuff that WinDBG can do that Visual Studio's debugger can't begin to touch. Searching memory, viewing the process' heaps, more sophisticated breakpoints, and so forth.
I also have a similar ritual for my New Year resolution: never launch Visual Studio. I go as far as to using cdb (command-line debugger that is part of the debugger tools) but, as was already said, there are always subtle issues that make it hard to stick with.