Troubleshooting
If you are new to TeamCity Add-in 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 keep abreast of the newest features available, read .NET Tools Blog
To report a bug or to request a new feature, 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.
Use Logs
If you experience any problems with TeamCity Add-in, 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 TeamCity Add-in 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 TeamCity Add-in as well as error messages from TeamCity Add-in core subsystems. If necessary, you can use additional argument to switch between different levels of log messages:
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.