Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio
All postings are provided AS IS
with no warranties, and confer no rights. Additionally, views expressed
herein are my own and not those of my employer, Microsoft.
Microsoft has an internal program for testing hotfixes that apply to Windows XP SP1 that asks some employees to not install XP SP2. Some of the people in this program have wanted to install VS 2005 and when they tried, they ran into the blocks in VS setup that require XP SP2 to be installed. VS 2005 setup does not have any technical requirements on XP SP2, but the block is in place to encourage everyone to upgrade to SP2, and also to reduce the test matrix. If you are running into this block and really need to install VS 2005 on a system that is running Windows XP without SP2, you can use the following steps. Please note that these steps are not officially supported and I would recommend installing XP SP2 before installing VS 2005 if at all possible:
Important note - if you use the above option, none of the prerequisites for Visual Studio 2005 will be installed. You need to make sure to manually pre-install Windows Installer 3.1, the .NET Framework 2.0 and the MSXML 6.0 Parser using the setup packages located in the wcu subfolder on the VS 2005 DVD. Failure to do so will result in errors during the VS installation process.
Once VS 2005 is installed, you will run into a separate block while trying to install MSDN. To workaround this, you can use the same registry-based workaround listed above, or do the following:
Note: after changing the CSDVersion registry key or modifying msdn.msi using Orca, you will need to use the following command line to install MSDN: msiexec /i msdn.msi SETUP_EXE=yes
<update date="8/26/2005"> I didn't specify clearly enough when I posted this last night that these steps are not "officially" supported, I must have been a little tired and left off the disclaimer I normally write when I post tips like this. I've added it above.
<update date="11/8/2005"> After receiving email from Fabrice based on the comments posted here, I realized that there is an additional step needed to install MSDN after using the workarounds listed above. I've updated the steps accordingly </update>
<update date="4/5/2006"> Added a caveat to option 1 above that you must manually install prerequisites in order to use this option </update>