views:

42

answers:

1

To start, this may be a useful link: http://www.ndepend.com/NDependConsole.aspx

As anyone who has used Visual NDepend may know, with NDepends you need to import project / solution files, and the corresponding output directories, namespaces, and assemblies are added to the NDepends project.

The problem I have, is I have TONS of these projects and solutions to add. It seems ridiculous to sit there for 45 minutes adding 300 solutions click by click. There must be a way to create an NDepend project file from a list of the paths to these solution / project files.

My first thought was to find the same information NDepends does (output directories, used namespaces and output executables dll's, etc) and programmatically create the NDepend project as a massive string. However, this seems like unnecessary work.

It would be nice if there was a way to invoke the command line and target specific projects, not output directories, as some of the projects have PostBuild tasks to copy assemblies to different directories, some projects specify the output directory as an upward relative path (ie ....), and so it isn't safe to assume that the output directory of a project is the same directory it is in.

Any ideas?

+1  A: 

Stefan, I am the lead developer of NDepend. So far the best way to create these projects files is to do your own file/dir program searcher and generate the simple .Ndproj XML yourself. We are aware of this need for large projects and will provide a kind of framework in the future, I hope in 2011.

Patrick Smacchia - NDepend dev
Yeah, I ended up taking this approach. As a side note, could I get your autograph?
Stefan Valianu
How can I get schema file for .ndproj xml file? Or simple .ndproj file contains full schema?
Ant