I'm giving NDepend 2.2 a run to see how I can integrate it in with my continuous integration process along with doing some of the other cool things that it can do.

On the company's website NDepend is described as:

... a tool for .NET developers that allows controlling the complexity, the quality and the evolution of .NET code. NDepend analyses source code and assemblies and generates a report. A GUI allows to visualize, zoom and control any part of the code.

The controlling part is a bit of a stretch.  NDepend gives you a great overview of your code, but as far as I could tell, you need to modify your code just as you always would, within your IDE.  Given that, the insight into the code is pretty cool.  Managers and programmers alike will love the visual feedback that NDepend can output.

Managers will like it because they will be able to see changes in builds.  Programmers will like it because a lot of times, the changes in code aren't visual.  For example, if you're writing a ton of business logic, there's not going to be any changes to the GUI.  In the past I've noticed that managers get a little antsy when things visually aren't changing, so NDepend could fill a gap there.

Getting started with the program is a little different.  There is no installer, you have to enter a code into their website, and then copy and paste an XML file into your installed directory.  Once that's going you have a couple of exe's to play with.  I've only really played with VisualNDepend.exe so far, but after a few button presses I got some pretty neato visuals.

To start I wanted to work with my current project, so I selected "Create New Project initialized from a VisualStudio 2005 solution or project".  Despite the spelling error :) the process was pretty simple, point to your solution file

and you'll get an input screen that will show all of the related assemblies (application and framework).  On mine a few were missing, like System.Web.Extentions, and I'm not sure why.  It didn't seem to change the output though, so I'm not too concerned. 

You first need to save your NDepend project when you've got it situated, then you press the "Play" button.

 This will go through the motions and bring up a huuuge report that outlines your solution.  One suggestion I would make here would be to break the report down into multiple pages so that I could print out sections.

On this report you will get all the pretty graphs and visuals that managers will like, but you'll also get some deep code analysis that you can use to make your code better.  All in all, pretty cool and useful stuff.