If you want Exposé on Vista...

Quoted: I'm kinda tired of these showy Vista window flyaround things myself, but if you're aching for a Exposé-like Vista action, Switcher may be it.

I just noticed the default power setting on my Vista dev box is "Balanced" -- meaning it goes to sleep after awhile. I wonder if this is why cannot connect to remote desktop from home.

Quoted: The default "off" state is now the new Sleep power state. Just press the power button on the Start menu or on your PC, and your PC will automatically save your current session to memory, and then quickly enter into a very low power state. It will also save your session to the hard drive, so you can access it even if the memory loses power. Then, when you want to resume your computer use, just press the power button on your PC. Your PC will turn on in seconds, and be just how you left it last time.

I can't get to my Vista dev machine from home. Maybe some of the tips in this thread will help...

Quoted: I can't for the life of me work out to enable remote desktop in Vista so that it works from XP (that is connecting to the Vista box from XP). The option to disable remote desktop from Vista only is greyed out. Any clues?

A little more on IIS 7...

Quoted: Each virtual directory must be assigned to an Application Pool and the Application Pool must be configured to run either in Integrated Pipeline mode or use the classic ISAPI mode.
...
You may wonder if that will break your applications with an invalid schema? Nope. Luckily Microsoft built ASP.NET 2.0 with support for the IIS 7 schema so these modifications will not break existing applications even if they are running on versions prior to IIS 7.

Yet another roadblock to getting my app working under Vista.

Quoted: When you initially try to run a web application with IIS7, it'll bitch at you and tell you to either migrate the application or run it in a classic app pool. I decided I would migrate my application since I'm sure I'll have little choice in the future.

One more helpful tip for getting started with ASP.Net on IIS 7.

Quoted: There is one more step involved in enabling ASP.Net on your Windows Vista machine. Follow the procedure in previous article to get to Panel for Windows Program and enable the appropriate sections under Internet Information Services > World Wide Web Services > Application Development Features. If you enable ASP, ASP.Net, Server Side Includes etc., your settings may look like the following image.

The metabase is dead...IIS configuration is now done with configuration files consistent with .Net configuration files.

Quoted: One of the most common problems with IIS to date has been the centralized and opaque nature of the IIS Metabase (which holds all the configuration data for the IIS server). It required an administrator to update the settings, and you were in serious problems if the metabase ever got corrupted. So it was very exciting to hear that the metabase is now officially dead. All configuration is now persisted in XML configuration files, and this even trickles down to the web.config files of the individual websites. Take for example the task of adding a default document to be served for a website, which can now be defined in its own web.config as such...

Hopefully this saves others some time. About two hours into my Vista upgrade, it failed and rolled back. Then, per the advice below, I removed IIS and tried again...it worked!

Quoted: The first place I looked, setuperr.log, only brought about frustration, anger, and resentment. Apparently Generic Command ({81a34a10-4256-436a-89d6-794b97ca407c}) failed, and that's why the rollback occurred. Yeah..
...
You have to be kidding me.
...
Someone at MSFT then posted, "let me see your setupact.log file". Apparently, the relevant data I needed was buried in that pile. It was like searching for a needle in a cow pie, but then, there it was. Generic Command was identified: IIS Metabase upgrade.

Despite the rant from Joel (which I agree with), I and others I've talked to are pretty happy with Vista.

Quoted: Moishe Lettvin, who spent a year working on the menu I criticized yesterday: “So that nets us a conservative estimate of 24 people involved in this feature.”