DotTrace plugin to TeamCity



I'd like to ask for some help about setting up the DotTrace plugin for one of our TeamCity builds - so far I've followed the instructions here, and got a build that sometimes works:


However, this is sometimes failing because the build produces two snapshots (snapshot.dtp and snapshot-2.dtp).

After much trial-and-error I've found out that sometimes the reason this fails is because my tests sometimes appear in the first .dtp file (which is the one used by DotTrace's Reporter.exe), and sometimes in the second file.

The other .dtp file appears to be associated with the nunit3-console.exe program, and so should be excluded, since I've added this program to "Process Filters" in the TeamCity build setup:


(I've tried every combination here, including entering the fully qualified file path)

This has the effect of adding the following line to the dotTrace.project.xml file when the profiler is run:


My understanding is that this should stop the named process from being profiled (so that the extra .dtp file isn't produced. However when the build is running, I see the following lines in the log file:

[16:01:04][Step 12/14] dotTrace Console Profiler 2018.3.2 build 777.0.20190124.112417. Copyright (C) 2019 JetBrains s.r.o.
[16:01:10][Step 12/14] Profiling in progress...
[16:01:10][Step 12/14] Executable='[file path]\nunit3-console.exe' (non-child) is being passed for filtering
[16:01:10][Step 12/14] Passed filter executable='[file path]\nunit3-console.exe'

This is showing that the nunit3-console.exe is not being excluded, as the filter would suggest.

Does anyone know of a fix for this?


The closest advice I can find is here, which appears to suggest what I'm doing, but is only for NUnit 2:


Thank you very much,



Please sign in to leave a comment.