The Microsoft Visual Studio 2005 Service Pack 1 Update for Windows Vista addresses issues that are related to Windows Vista enhancements. This article lists known issues with the installation of the Visual Studio Service Pack 1 Update for Windows Vista and with its features.
In order to build Web projects Team Build must have permissions to compile ASP.NET apps. The current Team Build setup configures these permissions via a call to aspnet_regiis. On Windows Vista this call fails when IIS is not present and this causes setup to fail and perform a roll-back. Customer must install IIS before installing Team Build. Since IIS is not necessary they may uninstall it after Team Build is installed.
Visual Studio Express Editions use the BITS service to download the install packages. Anyone attempting the install will need to give elevate administrator permissions to the setup utility to run it. However these elevated permissions do not flow onto BITS so the download fails when a standard user runs as admin.Manually download the install files as described here or run the install from an account with administrative permissions.
All Visual Studio products will fail to install with an error message saying “You need to install Windows XP SP2 before you install Visual Studio”. This happens due to the way detection logic is structured. We do not recommend installing VS in compatibility mode and there is no workaround to this scenario.
After upgrading to Windows Vista, various project templates in the New Project dialog may be missing.Open an command prompt with elevated administrator permissions and run the command “devenv.exe /installvstemplates.”
When a corporation deploys Visual Studio to their developer desktops using the Active Directory deployment scenario (as described here) the setup will fail because it tries to install the .NET Framework 2.0 which is already installed on Windows Vista.Manually remove the check for the .NET Framework as documented in Section 5.3 of the Enterprise Network Deployment Readme.
you can find more information on Visual studio 2005 vista permissions issues here: http://msdn.microsoft.com/en-us/vstudio/aa964140.aspx