|
-
Sep 24th, 2003, 12:26 PM
#1
Thread Starter
Lively Member
Debugger
I've been trying to debug an asp.net application on my localhost. Fine, been working fine all day. All of a sudden it decides not to work. Tried rebooting the machine, still doesn't work, tried restarting the IIS admin service, still doesn't work, tried restarting the debugging service, still doesn't work. I'm getting fired if I don't have this project finished by the end of the week and my ex wife is squeezing me till the pips squeak.
Can anyone advise as to why I'm having these problems (the debug problems that is).
Many Thanks,
AuldNick
-
Sep 24th, 2003, 12:37 PM
#2
Explain "doesn't work". Are you getting an error? What happens exactly? What was the last thing you changed?
-
Sep 24th, 2003, 01:12 PM
#3
Lively Member
I had the same problem. Here is how I got it to work in ASP.Net
1. Launch the App (either from the developer or directy from IE)
2. Back in the developer, choose Debug-Processes
3. Click on the process for aspnet_wp.exe then click on "Attach.."
4. If you are only doing code, then choose "Common Language Runtime". then click "OK"
you are now attached to your process. Go back to the web site and do your work. When it gets to the break, the developer will receive the focus and you can then step through code from there.
-
Sep 25th, 2003, 04:34 AM
#4
Thread Starter
Lively Member
Thanks for that, the bit about the firing and the ex was a joke by the way, hope it didn't come out like emotional blackmail.
Very grateful nonetheless.
Cheers,
AuldNick
-
Sep 25th, 2003, 04:38 AM
#5
Thread Starter
Lively Member
You are right "Doesn't work" is a bit glib, but to be honest, it's the best description I could think of, it simply stopped working. Made no change to any settings, and when I stop the page, it asks me if I want to stop debugging, although there's no debugging going on, despite me having breakpoints everywhere.
This seems to happen to me alot with debugging web applications whether it be local or remote, using classic asp or .net. They seem to work fine for a while and for some reason decide to stop, never to repair themselves again. I can't even debug client side javascript any more, which used to make life so much easier.
I'm not saying I've not done something to prevent it from working, but I just can not even begin to think of what!!
-
Sep 25th, 2003, 09:50 AM
#6
Make sure the project is in Debug mode and not in Release mode. No breakpoints will fire if you try to debug in Release mode.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|