Re: Command line interface

Matthew Mastracci wrote:

>Options (use quotes around any arguments containing spaces)
>  /r:<file>        The application to profile
>  /w:<workingdir>  Specifies the working directory for the application
>  /a:<args>        Specifies command line arguments
>  /v               Returns the version of nprof and exists
>
>  
>
Thanks Matthew.
The NUnit Addin author and I have been working with this. We can get 
Nprof to run in response to a "Test With..." menu click and it seems to 
do everything it should. However, the profiling data does not cover the 
namespace we are testing.
Am I right in thinking that the "/r" argument also defines the namespace 
for which to provide data?
For us to run the tests, the "/r" argument has to point to the NUnit 
Addin TestRunner executable. The desired namespace, however, is that for 
which we are running the tests. Does that make any sense? :-s
Whereabouts in the code should we be looking to find where the shown 
namespaces are specified?
Is there another way to do this?
Thanks for you help.

Michael J Kaye

**EPOS Team
STL Ltd



_____________________________________________________________________
This e-mail has been scanned for viruses by MCI's Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com .


-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html