Debugging dump files created on another machine

Visual Studio can analyse dump files for .NET4 processes in a similar fashion to how you debug when running an application locally.

This is handy when machines running your application can't easily be debugged (eg client or production machine)

Creating a dump file using Task Manager is easy (from Vista onwards) - simply right click the process and choose create dump.

However, If you want to take the .dmp file and analyse it on your own PC you need to ensure you have taken the correct dump. (assuming you want to do Managed Debugging in Visual Studio 2010, I'm not talking about WinDBG)

Consider the matrix below:

If you are running a 32bit OS and developing an app that targets x86 but deploying to a 64bit server then the yellow box is your scenario.

There is no standalone download page, you have to get it via the Windows SDK If you're in a panic/hurry the filename is dbg_x86.msi and a quick google turned up this direct link which worked as of 29th Aug 2010.

adplus.exe -hang -pn DebuggingExampleApp.exe -o c:\temp