I'm trying to automate the process of opening crash dumps for managed applications and retrieving the stack trace. Windgb works sometimes, but getting it to load the correct version of sos.dll is a nightmare unless the machine processing the dump is practically identical to the machine where the dump occured.
Visual Studio, on the other hand, does the job simply. I open the dump, go to the immediate window, and type
.load \\<machine where dump occured>\c\windows\microsoft.net\framework\v2.0.50727\sos.dll
!clrtsack
And eveything works just fine.
Can I script this process in visual studio? If not, is there a back end debugger used by visual studio that is the same as windbg?