(2005) Debugging Anything and Everything.

[rjbudz]

Since installing VS 2005, at start up of applications, I sometimes get a dialog asking me if I want to debug the application.

Every time any app (and we're talking ANY application that I want to run, not just my VS apps) hits a snag, I get this dialog, and the program aborts. Prior to this, the apps would just continue on their way, without a problem.

Unfortunately now they don't run.

Short of uninstalling VS (which will make my job a bit tougher) how do I teach it to leave any program outside of the IDE alone?

[Troy Lundin]

I believe when you install vs it becomes your default debugger. Maybe there was no default debugger before and so the application couldn't be debugged.

I get the dialog also, but only when errors occur. If all of your applications keep failing then you may want to get updates for them or try some alternatives.

[rjbudz]

All applications don't fail. Just one or two, but consistently. I agree that there was previously no default debugger. But the problem is that I don't need, or want, to debug out-of-the-box applications. I have enogh on my plate debugging my own. Much less look at assembly language (shutter!).

If the app would run when I dismissed the dialog, I could pretend to be happy, but it doesn't. Updating applications that previously ran just to appease VS seems wrong to me. Especially since not all apps HAVE updates.

[Troy Lundin]

Check out this link: http://www.microsoft.com/resources/d....mspx?mfr=true

I did a quick google search and it showed up. Basically, go to the following registry key: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\AeDebug and erase whatever is in the Debugger value. Also, if you set the Auto value to 1 no dialog will appear.

It also tells you how to make Dr. Watson the default debugger once again.
Just type 'drwtsn32 -i' in a command prompt.

Hope this helps.