Debugging NSE Under Vista - Comments Microsoft?   

Hi All,

This is a renewal of thread that was posted a while back about strange
behavior while debugging NSE's under Vista.  As Chuck Chopp noted, it
might have something to do with UAC.

Using VS2005, one sets Explorer.exe to be the launch process to debug
the current project that is the DLL representing the NSE.

Then one starts the debugging session.

Normally, VS2005 would then launch _one_ new Explorer process, and
that would be the end of it. Of course, one must first  fiddle with
the various "BrowseSeparateProcess" flag and friends, but after that,
one new process is what one normally gets.

On my development machine, under Vista, the following happens instead
when I start the debugger:

1. In addtion to my desktop Explorer.exe process E0, a new Explorer
process, E1, gets launched.
2. VS2005 debugger prints in output window all the DLL's being loaded
by E1, as usual.
3. E1, after loading all its DLLs, lauches a third Explorer.exe
process, E2. E1 then immediately exits.
4. VS2005 stops debugging because all threads of E1 have exited.
5. E2 is left standing as a separate, unattached process. I must
explicitly attach to it to debug it.

For the application developer who spawns Explorer.exe under the
debugger maybe 50-70 times/day, this manual attaching can be very
annoying.

For Microsoft, I have two questions:

1. Why is this happening?
2. What must I do to make it stop?

Much thanks in advance for a definitive answer. :)

-Le Chaud Lapin-

date: Wed, 20 Feb 2008 12:49:26 -0800 (PST)   author:   Le Chaud Lapin