View Single Post
  #18 (permalink)  
Old February 25th, 2005, 07:28 PM
paulwade paulwade is offline
Registered User
 
Join Date: Feb 2005
Location: San Diego, CA, USA.
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Oh, and one more thing -- after installing the SDK -- sometimes the path to the debugger is (for some odd reason) not added to the PATH environment variable. This can be done manualy by:

* Right Clicking on My Computer and selecting Properties

* Clicking on the "Advanced" tab

* Clicking on the Environment Variables button

* In the second (lower) pane of the new window, scroll down (if necessary) and select the "Path" variable and highlight it. Then click on the Edit button.

* In the second field ("Variable Value") -- you will need to scroll all the way to the end and put a semi-colon before putting the path to the cordbg.exe file.

* This path is usually (by default):

       C:\Program Files\Microsoft.NET\SDK\v1.1\Bin
* Click on OK, then click on OK again, then click on OK yet again

* (No need to reboot -- the path is now set -- and cordbg.exe can be found)

* Now that it can be found, run the offending application again

* When the error pops up -- click on the Cancel button to show JIT debugging

* Once cancel is clicked -- voila! -- you will no longer receive the error -- and instead a DOS Window will open that shows specific info on what exceptions are causing the error.

Again, I hope this helps! Let me know if you have any questions! :)

     -- Paul


Reply With Quote