• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 12375
  • Last Modified:

How to Disable the JIT Debugger "cordbg.exe"

I am trying to find a way to remove the "cordbg.exe" reference from my application (if possibly) so I do not get an error that the JIT Debugger can not be found when running the application on a machine that does not have the cordbg.exe program to call when the application starts.

Is this possible or do I need this to run on every computer that uses my application ?

I think that if I install the .net sdk on the machines then it will install the cordbg.exe program but I do not want to have to install the SDK on every machine or do I need too.

thanks
teamels
0
teamels
Asked:
teamels
  • 3
  • 2
1 Solution
 
jhanceCommented:
This is the debugger for "exceptions of last resort".  The solution is to catch all possible exceptions in your code so that the debugger never gets called.  If you are seeing this, you have unhandled exceptions in your code...
0
 
teamelsAuthor Commented:
If there were unhandeled exceptions wouldnt Visual Studio catch this upon bulding the solution?
If I have an exception visual studio so far sees this and does not let the program build and also lets me see where the exception took place and a suggestion on how to correct this.

Do we need to call the cordbg.exe JIT Debugger to run even if the program seems to run just fine.

Thanks
teamels
0
 
teamelsAuthor Commented:
If it can't be disabled then how do we install the bloody bugger ? on client machines already running .NET V1.1

thanks
teamels
0
 
jhanceCommented:
No, there is no requirement at handle all exceptions.  That's why Windows catches anything you don't catch.

Once again, catch ALL possible exceptions in your code and you won't need any JIT debugger.  This is not as hard as it sounds.  Just enclose the top level function in your application in a try/catch block.  You don't have to actually do anything other than catch the exception.  You can just output an error and exit, or whatever you want.
0
 
teamelsAuthor Commented:
I see now.  I placed the Try, Catch, Finally in the below section, which I never thought to do because it was pre-generated code by Visual Studio.  This shows that I have a reference to a .VB file that is only installed on my development computer, not any others.

#Region " Windows Form Designer generated code "

    Public Sub New()

        MyBase.New()

        Try
            'This call is required by the Windows Form Designer.
            InitializeComponent()

thanks
teamels
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now