BertanAygun
commented
2 years ago @CartBlanche, are you asking for an existing extension using in-proc VSSDK?
There are couple logging paths for Visual Studio currently:
-
%APPDATA%\Microsoft\VisualStudio\17.0_
\ActivityLog.xml: This may contain some information about the exception before a crash depending on where the exception occurred. Your component can also log here using https://docs.microsoft.com/en-us/visualstudio/extensibility/how-to-use-the-activity-log?view=vs-2022. -
%TEMP%\VSLogs: This is the output for many components utilizing centralized logging but may not provide information about extensions.
If you want to create a log entry here from your VSSDK based extension, you can use TraceConfiguration.CreateTraceConfigurationInstanceAsync method (see links below).
For extensions using the new out-of-proc SDK, code should be using the TraceSource instance via dependency injection. This instance is already created via using TraceConfiguration class.
- For crash dumps, the best option would be to ask your users to run procdump on their machine monitoring for a crash and share the resulted dump file with you directly. https://docs.microsoft.com/en-us/sysinternals/downloads/procdump. We have no process for sharing crash dumps with extension developers at this point.
CartBlanche
What is the best way to log, or see, the stack trace when out extension crashes and takes the IDE with it? Is there a Best Practices document or suggestions? Maybe writing things to /log perhaps?
We'd like customers of our extension to be able to send us log, so we can see where our extension crashed for them.