I am trying to automatically open an NDepend project when the solution creates an automatic build in TFS2010.
This is related to this previous question. The above post is where I tried (and failed) to integrate NDepend code indexing software with Team automated build through messing with the XML of my solution.
I decided that since I did not have time to mess with XML, I would try a different route. In another program that I developed, I used
System.Diagnostics.Process.Start("blah.txt");
to start Notepad to start and open the text file "blah.txt."
I decided that I could use the same concept to help me with this NDepend integration. So I researched MSDN to find out if I can learn more about the Process.Start method. And using this example
Process.Start("IExplore.exe", "C:\\myPath\\myFile.htm");
I replaced on my own paths what I think should open the project file "myProj.ndproj" inside the VisualNDepend application, like this
System.Diagnostics.Process.Start("C:\\tools\\NDepend\\VisualNDepend","C:\\myProj\\myProj.ndproj");
I can take this example and configure it out of context, I'm not sure, but it seemed to me that what I tried should work. The solution was built perfectly without any errors, but VisualNDepend did not execute.
It finally struck me that I was trying to use this code, which will only be executed when the program starts, when I really need it to run, when the program is built in TFS and Visual Studio.
, - TFS VS, , . . "Googling" .
- , ? , # ? XML, ?