How to get dotCover logs Follow

In some cases, to troubleshoot your issue, the dotCover support team may ask you to provide dotCover log files. The procedure of taking logs differs depending on the way you run dotCover: in Visual Studio, standalone, or using the console runner. By default, log files are saved to the %Temp%\JetLogs folder.

Choose article section corresponding to your environment:

1. dotCover integrated in Visual Studio
2. dotCover in Rider
3. dotCover standalone
4. dotCover console runner
5. dotCover dotnet global tool

6. dotCover console runner in JetBrains TeamCity

dotCover integrated in Visual Studio

To take dotCover logs

1. Start Visual Studio with the following command line argument:
   /ReSharper.LogFile C:\log\dotcover_log.txt /ReSharper.LogLevel {Level}
   Where:
• C:\log\dotcover_log.txt : path to the resulting log file;
• {Level} : log level. In most of cases Verbose level is enough, so please use it as a default level besides cases when one explicitly asked you to collect logs with Trace level.

For example, to run Visual Studio 2015:
"C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.exe" /ReSharper.LogFile C:\log\resharper_log.txt /ReSharper.LogLevel Verbose

2. Reproduce your issue.

By default, if you do not specify path to the log file in step 1, the file will be saved to the %Temp%\JetLogs folder under auto-generated names. Note that in this case /ReSharper.LogFile must be the last argument.

To take dotCover core logs

1. Delete the %Temp%\JetLogs folder if it exists.
2. Close any open Visual Studio instances with integrated dotCover.
3. Start Visual Studio.
   
4. Press Ctrl+Shift+Alt and while holding it, run coverage analysis to reproduce the issue.
5. The Coverage Configuration window will be opened.
6. In the Coverage Configuration window, press Ctrl+Alt+Shift+F11 to enable expert options.
7. Click the Expert options button.
8. Check Enable logs (do not check any settings in the Log flags section unless you were asked by the dotCover support team!).
9. Click Save.
10. Click Run to run coverage analysis.

Log files will be saved to the %Temp%\JetLogs folder under auto-generated names.

dotCover in Rider

1. Navigate to Help | Diagnostic tools | Choose Trace Scenarios and enable scenarios for DotCover and DotCoverExternalProcess;

2. Reproduce the issue;

3. Disable Trace scenarios at Help | Diagnostic tools | Choose Trace Scenarios;
4. Collect the full log bundle via Help | Collect logs and send the resulting archive.

To take dotCover core logs

1. Start Rider in Internal mode
2. Go to File | Settings | Build, Execution, Deployment | dotCover
3. Specify profiler core log masks provided to you in Core: line.
4. Reproduce the issue;
5. Remove logs mask at File | Settings | Build, Execution, Deployment | dotCover | Core;
6. Collect all Rider logs using Help | Collect Logs menu and send the resulting archive.

dotCover standalone

To take dotCover logs

1. Start dotCover with the following command line arguments:
   /LogLevel={Level} /LogFile=C:\log\dotcover_log.txt
   Where:
• {Level} : log level. In most of cases Verbose level is enough, so please use it as a default level besides cases when one explicitly asked you to collect logs with Trace level;
• C:\log\dotcover_log.txt : path to the resulting log file.

For example:
%LocalAppData%\JetBrains\Installations\dotCover09\dotCover.Shell.exe /LogLevel=Verbose /LogFile=C:\log\resharper_log.txt

2. Reproduce your issue.

By default, if you do not specify path to the log file in step 1, the file will be saved to the %Temp%\JetLogs folder under auto-generated names.

To take dotCover core logs

1. Delete the %Temp%\JetLogs folder if it exists.
2. Start dotCover standalone.
3. Run coverage analysis.
4. The Coverage Configuration window will be opened.
5. In the Coverage Configuration window, press Ctrl+Alt+Shift+F11 to enable expert options.
6. Click the Expert options button.
7. Check Enable logs (do not check any settings in the Log flags section unless you were asked by the dotCover support team!).
8. Click Save.
9. Click Run.
10. Reproduce your issue.

Log files will be saved to the %Temp%\JetLogs folder under auto-generated names.

dotCover console runner

To take dotCover logs

1. Start dotCover console runner with the following command line arguments:
   /LogLevel={Level} /LogFile=C:\log\dotcover_log.txt
   Where:
• {Level} : log level. In most of cases Verbose level is enough, so please use it as a default level besides cases when one explicitly asked you to collect logs with Trace level;
• C:\log\dotcover_log.txt : path to the resulting log file.

For example:
%LocalAppData%\JetBrains\Installations\dotCover09\dotCover.exe /LogLevel=Verbose /LogFile=C:\log\resharper_log.txt

2. Reproduce your issue.

To take dotCover core logs

1. Start dotCover console runner with the additional command line argument: /CoreLogMask=[masks]
   Where [masks] is a string with core log masks separated with a semicolon (;). Normally, the dotCover support team provides you with the core log masks you should specify.
   For example:
   %LocalAppData%\JetBrains\Installations\dotCover09\dotCover.exe /LogLevel=Verbose /CoreLogMask=PdbGt;MetaDataGt;PdbBridge /LogFile=C:\log\resharper_log.txt
2. Reproduce your issue.

dotCover dotnet global tool

To take dotCover logs

1. Start dotCover console runner with the following command line arguments:
   --dcLogLevel={Level} --dcLogFile=C:\Temp\dotcover_log.txt
   Where:
• {Level} : log level. In most of cases Verbose level is enough, so please use it as a default level besides cases when one explicitly asked you to collect logs with Trace level;
• C:\Temp\dotcover_log.txt : path to the resulting log file.

For example:
$ dotnet dotcover test --dcLogLevel=VERBOSE --dcLogFile=dotcover.log

2. Reproduce your issue.

dotCover console runner in JetBrains TeamCity

To take dotCover logs

1. Open your build configuration in TeamCity.
2. Add a new parameter teamcity.agent.dotCover.log with the value %system.teamcity.build.tempDir%/dotCoverLogs.
3. Run the build.
4. In build artifacts, choose show hidden artifacts and find the file .teamcity/.NETCoverage/dotCoverLogs.zip.

To take dotCover core logs

1. Open your build configuration in TeamCity.
2. Add a new parameter teamcity.agent.dotCover.log with the value %system.teamcity.build.tempDir%/dotCoverLogs.
3. Open the required code coverage build step.
4. In Additional dotCover.exe arguments, specify /CoreLogMask=MetaDataGt;InstrumentationGt;PdbGt;PdbBridge
5. Run the build.
6. In build artifacts, choose show hidden artifacts and find the file .teamcity/.NETCoverage/dotCoverLogs.zip.