Re: Re: Command line interface

Matthew Mastracci wrote:

> At the current moment, all namespaces within the application are 
> available within the profiler information.  We might be able to 
> provide an option to filter certain namespaces out by default - for 
> instance, removing any NUnit.* namespace.  There isn't any sort of 
> functionality supporting this right now, however.
>
> Let me know what you need and we can figure out the best way to do it.
>
Thank you, again, for responding so quickly.
Here's what we're trying to do.
NUnit Addin gives adds some options to the context-menu in the code 
window. One of these is a "Test With..." menu. This means you can 
right-click on a namespace, unit test, or test fixture and run the 
specified test(s) immediately. The "Test With..." menu allows you to use 
the debugger, or Mono to run the tests. This allows you to, for 
instance, step through your tests with the debugger.
We want to add an entry to the "Test With..." menu that would allow us 
to run the tests with Nprof, hence, allowing us to profile the tests. 
This would be an enormously useful feature.
The "Test With..." menu entries are controlled by bat files. The bat 
file we currently have for Nprof contains the following line:
    "C:\path_to_nprof_binaries\nprof.application.exe" /r:%1 /a:"%~2 %~3 
%~4 %~5 %~6 %~7 %~8"

When the bat file is run, the command-line looks like:
"C:\NprofPath\nprof.application.exe" 
/r:"C:\VsProjectPath\bin\Debug\MethodExecutor.exe" 
/a:"file:///C:/NUnitAddinPath/NUnitAddin.TestRunner.Runtimes.DLL 
NUnitAddin.TestRunner.Runtimes.TestRunnerRuntimes Main 
http://222.22.2.222:4027/TestListener_0cb99eb5-49ce-4ef8-bc6e-de7027192a93 
http://222.22.2.222:4027/TraceListener_8b4e1a30-0929-4b42-9f32-2ea729231744 
C:\VsProjectPath\bin\Debug\AssemblyToTest.dll 
NamespaceToTest.TestFixture.UnitTest"

This fires up Nprof, which in turn, runs the MethodExecutor executable. 
I am then presented with the profiling data for the System, Microsoft 
and MethodExecutor namespaces. However, the MethodExecutor namespace is 
from the NUnit Addin and I want the profiling data for the 
"NamespaceToTest" namespace. This is what led me to believe that the 
"/r:" argument defined the namespace to profile. Is this an incorrect 
assertion?
Do you think it will be possible to get the profiling data for the 
"NamespaceToTest" namespace?
I hope some of this makes sense. Thank you for any help you can provide.

Michael.

_____________________________________________________________________
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