cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

This product reached the end of support date on March 31, 2021.

Problem with Telerik JustMock profiler

sturmberger
Newcomer

We use Telerik's JustMock as mocking framework. It uses a profiler, but does not add it to the windows environment variables. The profiler is only enabled during running our unit tests.

After installing Dynatrace locally on our developer workstations, the JustMock profiler does not work anymore and we saw, that multiple variables were set for Dynatrace's profiling:

CORECLR_ENABLE_PROFILING=0x01
CORECLR_PROFILER={DA7CFC47-3E35-4c4e-B495-534F93B28683}
CORECLR_PROFILER_PATH_32=C:\Program Files\Dynatrace\Dynatrace 7.0\agent\lib\\C:\Program Files\Dynatrace\Dynatrace 7.0\agent\lib\dtagent.dll
CORECLR_PROFILER_PATH_64=C:\Program Files\Dynatrace\Dynatrace 7.0\agent\lib64\\C:\Program Files\Dynatrace\Dynatrace 7.0\agent\lib64\dtagent.dll
COR_ENABLE_PROFILING=0x01
COR_PROFILER={DA7CFC47-3E35-4c4e-B495-534F93B28683}

Of course this is not relevant for productive use of Dynatrace, where we don't have the JustMock profiler.
But I would like to know if there is an easy way of using both ,JustMock and Dynatrace locally on the developer systems ?

2 REPLIES 2

andreas_grabner
Dynatrace Guru
Dynatrace Guru

Hey Gunther

Sorry for the late reply on this. AFAIK there can only be one CLR Profiler Tool attached to a CLR. It is controlled through these Env Variables.

Dynatrace sets the Env Variables globally so that we can potentially instrument EVERY process that you want us to instrument. Another option though is to disable the Dynatrace .NET Agent Globally -> this can be done through the .net agent config tool and it will actually just remove these env variable on system level. NOW - your developers can then launch their application and in their startup script, e.g: in their .bat file just SET these Env Variable depending on which tool they want to use

Does this help?

Thanks for the reply - that is a feasible option.