-
Would it be possible to save the current state as a Visual Studio debugger snapshot in a file, This would be great for production, especially if we can generate such file whenever an exception is raised. It would make it easier to identify errors on the caller side. In addition, it would be great to store them in different folders, or file names with specific prefix based on the stack trace so they are grouped by cases (i.e. the exceptions generate in similar context are together, in the sense that if you fix one of those issues you'll probably fix all the issues in that group)
and
Thank you |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
This is a long-established capability. Create a minidump using Task Manager or programmatically using Then open the file (possibly on another computer) using Visual Studio: https://docs.microsoft.com/en-us/visualstudio/debugger/using-dump-files#BKMK_Open_a_dump_file You'll get full call stacks and locals etc as though you were paused while debugging. |
Beta Was this translation helpful? Give feedback.
This is a long-established capability. Create a minidump using Task Manager or programmatically using
MiniDumpWriteDump
.Then open the file (possibly on another computer) using Visual Studio: https://docs.microsoft.com/en-us/visualstudio/debugger/using-dump-files#BKMK_Open_a_dump_file
You'll get full call stacks and locals etc as though you were paused while debugging.