|
|
![]() |
|
|
Top | #1 |
|
OSNN Junior Addict
Joined: May 2008
Location: California
Posts: 17
Reputation: 0
Power: 50 |
|
|
|
|
|
|
Top | #2 |
|
XPista7eopard*ix
Joined: April 2004
Location: Chicagoland
Posts: 4,028
Reputation: 2947
Power: 168 |
1) you may want to wait more than 30 minutes before complaining about no one helping you.
2) Might be useful to provide more info like system specs, OS version, and, last but certainly not least, what your problem actually is. |
|
|
|
|
|
Top | #3 |
|
OSNN One Post Wonder
Joined: May 2008
Posts: 1
Reputation: 0
Power: 0 |
After Visual Studio is installed, the default behavior when an unhandled exception occurs is to show an Exception dialog that requires user intervention to either start Just-In-Time debugging or ignore the exception. This may be undesirable. To configure the server to no longer show a dialog when an unhandled exception occurs (the default behavior prior to installing Visual Studio), use the registry editor to delete the following registry keys:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\DbgManagedDebugge |
|
|
|
|
|
Top | #4 |
|
OSNN Junior Addict
Joined: May 2008
Posts: 8
Reputation: 0
Power: 50 |
Is there any particular set of actions you take that triggers the JIT? Under normal circumstances (and depending on your configuration, you should not see this unless an application is throwing an unhandled exception of some kind.
You should also be able to tell what executable is crashing. In any case, there isn't enough information in this thread for us to help you at this point. |
|
|
|
![]() |
| Bookmarks |
| Thread Tools | |
|
|