Not sure how long this has been around, but I just stumbled across this set of guidelines and tools to support multi-user access to a full Visual Studio .NET development environment via Terminal Services. The material was originally designed for the purpose of supporting a university development environment, but there's little here that wouldn't be of equal use in a commercial environment. It includes guidelines for systems administrators and developers on building and operating the system. This approach might be helpful if you're working in one of those corporate departments which are still wary of anything that deviates from a "standard machine build image" - something that I've heard many times from different customers. Academic users might also be interested in this presentation which details the experiences of Yale University who adopted a similar approach.