Troubleshooting
If you are new to dotCover or something goes wrong during your everyday work, there are several places where you can search for a solution, ask for advice, submit bugs, suggest new features or just talk to people that share the same interests.
To find answers to frequently asked questions or advice on how to avoid certain situations, look through issues in dotCover Knowledge Base
To keep abreast of the newest features available, read .NET Tools Blog
To share your experience with other people or get in touch with our developers, go to dotCover Community
To report a bug or to request a new feature, use the Feedback Center dialog or use the Issue Tracker. If you're submitting a bug report, please provide steps to reproduce it and attach the solution or some code sample that you work with.
In some cases when you report a bug, support team can ask you to provide dotCover logs. See how to collect logs.
To share information that is not meant to be public, contact the dotCover team via e-mail
Here are some most frequently asked questions about dotCover:
Do I need a license to use dotCover command-line tool? Answer
How to correctly specify arguments of a covered application for the command-line tool? Answer
Does dotCover support C++? Answer
Does dotCover support .NET Core? Answer
Use Logs
If you experience any problems with dotCover, you can also log the execution and pinpoint the problem. The logs could also be helpful to provide details on possible problems to the support team.
Logging in Visual Studio
When working with dotCover in Visual Studio, you can enable logging by starting Visual Studio devenv.exe with the following command line arguments:
/ReSharper.LogFile- The log will be saved in %TEMP%\JetLogs folder with auto-generated name./ReSharper.LogFile path_to_the_log_file- The log will be saved in the specified location.
By default the main log includes interactions between Visual Studio and dotCover as well as error messages from dotCover core subsystems. If necessary, you can use additional argument to switch between different levels of log messages:
Also, the logs from the workspace host (external process for each coverage session) are enabled when the main log is enabled; these logs are saved separately in the %TEMP%JetLogs directory.
If necessary, you can expand log output by enabling custom core logs. In this case besides errors, all information messages from the selected core logs are recorded.
Enable custom core logs
While holding Ctrl+Alt+Shift, run coverage analysis of unit tests in any of the available ways or start coverage analysis of the startup project.
When the Coverage Configuration dialog appears, press Ctrl+Alt+Shift+F11.
In the Expert Options dialog that appears, use check-boxes to enable the corresponding core logs.
Resulted logs can be found in the following locations:
Most of the core logs are embedded into the main log
Some of the core logs are stored as additional lgc*.tmp files in the %TEMP% directory.
The workspace host logs are stored in the %TEMP%JetLogs directory.
Logging in command-line tool
When using dotCover command-line tool, just add the following parameters to any of the commands:
- /LogFile
Enables the main log and saves it in the %TEMP%\JetLogs folder with auto-generated name.
- /LogFile=path_to_the_log_file
Enables the main log and saves it in the specified location.
- /CoreLogMask=Masks
Enables custom core logs, where
masksis a string with core log masks separated with the semicolon (;).You can find the full list of core log masks in the Expert Options dialog in Visual Studio (see above).
Locations for custom core logs are the same as described above for dotCover in Visual Studio.