Understanding the basics (UAC and VS2005)

Heck!

Have installed the now public Vista RC1, VS2005 and SQL Server 2005. (On a clean system)

Smooth ride, until I tried to install WebApplictionProject.
Just did not work, ended up with an error code! (How 1990)

Some googling brought me to forums.asp.net, where the tip to turn off UAC temporarily, solved it for me.
Great!

Turn on UAC again.

Time for some testing.
- Running as an ordinary user.
- Create a small file based web site.
- Hit the debugger, and the development server fires up.
- The debugger detaches and the development server stops. What now?

Nothing in error log.

Start without debugging works fine, and I can even attach the debugger, once the development server is up and running.

Maybe something is wrong with my setup and the development server?
Ok, no panic, I can test with the IIS.
Some tweaking with the application pool, permissions, just getting familiar with the new interface for IIS 7.

New tests.
No go, I am not allowed to debug!

Right click VS2005 to run as admin.
Hey it works!

With this UAC stuff, I figure it is ok to run with admin account, so I log off and log on again with an admin account, ready to do some more.

Guess what!
Not able to start debugging on the web server. Again?!
I just tried it didn't I? What is going on!?!


More googling took me to a blog about VS2005, UAC and installers. The tip was to run VS2005 as Administrator. (Lost the link, sorry).

Yeah, that was what I was doing when it succeeded previously.
Ok, give it a shot.

Hey it works! Both with IIS and the development server.
So now when I hit debug, does IE fire up with full administrator rights?

So much for no need to be an administrator any longer, when developing web-applications.

Or, do I still not know how to work in this new environment?

Any hints or pointers are appretiated.