Here's another question that I often get: How can I control which Team Projects a specific user can see in TFS?

A: In TFS 2008 this is the default behaviour! New projects will only be visible to the members of the project groups.

In TFS 2005 there's a different story. Here the behaviour is that all valid TFS users can see all projects. That of course won't give them rights to do things in the projects, but having a long list of projects can be confusing. The solution in this case is to create a role (i.e. "Denied users") with "View project-level information" set to "Deny".

Yesterday Microsoft announced the availability of the RTM version of Hyper-V, the new virtualization component of Windows Server 2008.

I'm a huge fan of Virtual PC. I use it more or less every day for development tasks and training because it's so easy to use. Having a way to deal with different environments without messing up your main configuration is priceless.

I've tried to use Virtual Server much the same way on a server scale but compared to VM-Ware it's quite limiting when it comes to guest OS management, such as resource sharing, support for physical hardware (where's the USB support?) and image handling. Hyper-V will likely change this so that we now can use the same infrastructure for virtual images both on desktops and servers.

And as for Team Foundation Server? It's supported as well! TFS 2008 still requires 32-bit OS on the application tier but a 32-bit OS can of course be hosted in Hyper-V on a 64-bit system. Brian Harry wrote about the implications of using TFS with Hyper-V technology in this post.

I've concidered using Windows Server as the OS for my laptop for a while. With Hyper-V now out the door my next laptop will run Windows Server 2008!