Strange Debugging Issue | Tech Off

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

DuNuNuBatman

Anyone else have this problem?

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.

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.

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?

Sven Groot
My name has 9 letters. Coincidence? I think not...

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.

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.