Strange Debugging Issue

Posted By: DuNuNuBatman | Sep 3rd, 2006 @ 9:42 PM
page 1 of 1
Comments: 7 | Views: 5623
#Sep 3rd, 2006 @ 9:42 PM
DuNuNuBatman
DuNuNuBatman

Alright, I am running a fresh copy of Vista RC1 and Visual Studio 2005 (woo hoo!!!)...
anywhoo, everything was running fine, but I noticed some strange behavior in the way that VS would start debugging. Normally when I would press F5, IE pops up and in the background you can see all of the VS toolbars hide away (this isn't the issue, I'm just trying to give as much info as I can).
When I define a break point now, VS will ignore it completely. I am guessing that the VS debugger is closing prematurely and that is why the breakpoints don't work.
Since the folks at Microsoft have been so kind as to dog food this for all of us, I was wondering if anyone else has noticed this and if there is a fix for it.

Sorry for my poor use of grammar, I typed this in a hurry. Any help is appreciated as I am lost on how to fix this.

Thanks

#Sep 4th, 2006 @ 10:54 AM
DuNuNuBatman
DuNuNuBatman
Anyone else have this problem?
#Sep 4th, 2006 @ 12:48 PM
DuNuNuBatman
DuNuNuBatman
Alright, it looks like I have fixed it... I set it to run as the administrator and now it works great.
So if anyone runs into the same problem here is the quick fix.
#Sep 4th, 2006 @ 1:32 PM
amotif
amotif
No Silver Bullet
DuNuNuBatman wrote:
Alright, it looks like I have fixed it... I set it to run as the administrator and now it works great.
So if anyone runs into the same problem here is the quick fix.


Oh, um, yeah. LUA does things to you like that. If you want to use what might be considered elevated privileges (like debugging) you might want to run the app (in this case your debugger/IDE) as administrator.
#Sep 4th, 2006 @ 2:53 PM
andur
andur
Strange, I've used the debugger under VS2005 and Vista many times without ever having to elevate it or provide any sort of administrator rights to it.

Though I don't do web-based stuff at all, so maybe that has something to do with it?
#Sep 4th, 2006 @ 3:18 PM
Sven Groot
Sven Groot
You can't have everything; after all, where would you put it?

I've seen this too. It happens only with IE, debugging anything else seems fine. It seem IE launches, the debugger attaches and it immediately detaches. Maybe something to do with IE protected mode, I don't know.

You can debug IE without having to elevate without any issues. All you need to do it start it first, then attach to it (using Tools/Attach to Process in VS). It's just attaching by starting it with F5 that doesn't work.

#Sep 14th, 2006 @ 8:16 AM
incola
incola
It seems that this bug is caused by using IE with Protected Mode enabled. The easiest way to fix this issue is to add the debugged site (http://localhost) to Trusted Sites zone which has Protected Mode disabled by default.
#Sep 14th, 2006 @ 6:52 PM
amotif
amotif
No Silver Bullet
I think Sven's right, too much time spent debugging elevated Integrity Level apps has skewed my experience.
page 1 of 1
Comments: 7 | Views: 5623