New
#11
I'll have to try the virtualization method i think Archie,
Will post back with results
I'll have to try the virtualization method i think Archie,
Will post back with results
The JIT problem is not exclusive to Windows 7.
I also maintain hybrid ASP / ASP.NET sites and would like to know how to get JIT to work when it doesn't.
I normally put in a divide by zero to start debugging a classic ASP page, then advance the (yellow arrow) current statement pointer and keep on debugging.
But when the divide by zero won't fire the JIT debugger in VS, it's really hard to debug.
I'm joining the thread hoping one of us finds an answer. I think I just lost JIT on one of my (Vista) machines where it worked previously.
Back again,
Hi Cornan, sorry to hear your suffering the same problem as me but glad I'm not alone.
I got XP running on a virtual machine on my laptop but it is not really practical to use this as a development environment.
I wish i had Bill Gates phone number & email as he'd be getting some pretty nasty messages right now.
Needless to say i still have not found the solution to this problem
Still making no progress on this one,
Anyone else out there found a fix for Just in Time Debugging Classic ASP on IIS 7.5 with Windows 7 ????
There must be an answer...
The Truth is Out There.................
Found on IIS Forums:
IIS7 Client Side Debugging Problem - Solved : The Official Microsoft IIS Site
Thanks for reply. My problem was couldn't debug on client side and found solution. Thanks anyway.
Solution for debugging problem is:
1- Push Win+R buttons and execute Run window
2- Copy/Paste this :
%windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpErrors -errorMode:Detailed3- Push enter button and thats all.
Dont know if that might help. I came to this thread because Arc posted for help elsewhere. this is the only related thing I could find.
Hi Thorsen,
Thanks for having a go at this one.
Unfortunately I had found that post and tried it before I started this thread. I have however reinstalled everything on my computer since then so i have just tried it again and still not getting the debugger to fire up.