Click to Rate and Give Feedback
MSDN
MSDN Library
Visual Studio 2005
Visual Studio
Debugger Roadmap
 How to: Enable/Disable Just-In-Time...
This page is specific to
Microsoft Visual Studio 2005/.NET Framework 2.0

Other versions are also available for the following:
Visual Studio Debugger
How to: Enable/Disable Just-In-Time Debugging

This topic applies to:

Visual Studio Edition

Visual Basic

C#

C++

J#

Express

No

No

No

No

Standard

Yes

Yes

Yes

Yes

Pro/Team

Yes

Yes

Yes

Yes

You can enable Just-In-Time debugging to launch the Visual Studio debugger automatically when a program, running outside Visual Studio, encounters a fatal error.

Procedure

To enable/disable Just-In-Time debugging

  1. On the Tools menu, click Options.

  2. In the Options dialog box, select the Debugging folder.

  3. In the Debugging folder, select the Just-In-Time page.

  4. In the Enable Just-In-Time debugging of these types of code box, select or clear the relevant program types: Managed, Native, or Script.

    To disable Just-In-Time debugging, once it has been enabled, you must be running with Administrator privileges. Enabling Just-In-Time debugging sets a registry key, and Administrator privileges are required to change that key.

  5. Click OK.

See Also

Tags What's this?: Add a tag
Community Content   What is Community Content?
Add new content RSS  Annotations
Doesn't help those without VS      Shark_D   |   Edit   |   Show History
These instructions don't help those people who have the script debugging tools installed, but not Visual Studio.
Tags What's this?: Add a tag
Flag as ContentBug
I had to think for a moment!      Wasted_Code   |   Edit   |   Show History
Hi @Everyone,

If you agree with the guys above, you need to use the Options menu in Visual Studio.

Just open a copy of Visual Studio and follow this instructions from the Options menu.

I have no idea how the just-in-time debugger is suppose to help the general coding community. Maybe if you are trying to write a virus in assembler and it throws a error, you can use this to see what write protected memory you tried to access, so you can use another address.

Cheers!


Tags What's this?: Add a tag
Flag as ContentBug
What the ***.      Lunisneko   |   Edit   |   Show History
I have just found out that in addition to the above problems there is another huge problem. If you have a trial that expires, there is no way to disable the JIT debugging "feature". Thanks again, Microsoft, for making my day ***!
Tags What's this?: Add a tag
Flag as ContentBug
HTH      SClark_AccessMVP   |   Edit   |   Show History

On this page, it shows the registry settings that affect this.

http://msdn.microsoft.com/en-us/library/5hs4b7a6(VS.80).aspx

  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger

  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\DbgManagedDebugger

  • Tags What's this?: Add a tag
    Flag as ContentBug
    Fail      IAM_NZ   |   Edit   |   Show History
    Using VS2008 and following these instructions have no effect on the JIT... it continues to pop up.

    Searching google I found a hack that suggests the following reg key value be set to 1 to disable the JIT

    (and this works for me)

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\DbgManagedDebugger

    When I manually set this value to 1 and open VS. The Managed check-box is not selected. If I select this check-box in VS I see that that value in the reg is updated to 16. If I then unselect the check-box in VS the value in the reg does not change and remains at 16... A bug perhaps?
    Tags What's this?: Add a tag
    Flag as ContentBug
    Processing
    © 2010 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks | Privacy Statement
    Page view tracker