About Windows Installer, the .NET Framework, and Visual Studio.
If you're attempting to install the Visual Studio 2005 Service Pack 1 Update for Windows Vista without having installed Visual Studio 2005 Service Pack 1 first on all applicable products, you will receive Windows error 1642, which reads,
The installer cannot install the upgrade patch because the program being upgraded may be missing or the upgrade patch updates a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch.
Some news outlets and blogs have reported that this would be or is a special edition of VS 2005 SP1 but it is actually a hotfix that installs on top of, and thus requires, Visual Studio 2005 SP1. The system requirements in KB929470 and on the download page also state that SP1 is required.
Also note that each localized hotfix targets more products than SP1. VS 2005 SP1 was split up into multiple patches to prevent the patch package from being even larger than it is. This is because of how files are shared across products and stored within a patch package. VS 2005 SP1 targets separately,
So, if you have both a VS Express SKU and a VS SKU installed, you'll need to download SP1 patch packages for each and install them first. Each patch may appear to install multiple times because many of our SKUs are comprised of multiple products that are each patched. Then install the Visual Studio 2005 Service Pack 1 Update for Windows Vista. If you later install another SKU, you will need to re-install both SP1 and the Vista update for that SKU.
I tried following your instructions about slipstreaming SP1 and KB929470 (http://blogs.msdn.com/heaths/archive/2006/12/16/slipstreaming-visual-studio-2005-service-pack-1.aspx)
and burned the resulting 3 GB administrative image to the DVD.
The installation started fine and ran about 1/3 of the file copy progress until a prompt popped up: "Please insert the disk: Microsoft Visual Studio 2005 Professional Edition - ENU Disk 1".
The log file indicated that it expected volume label to be "VSPROD1", while my DVD was named "VS2005SP1".
After burning another DVD with the proper volume label I tried to run setup again. It went about 2/3 through before popping up almost identical message:
"Please insert the disk: Microsoft Visual Studio 2005 Professional Edition - ENU Disk 2".
This time it wanted the volume label to be "VSPROD2". D'oh!
After wasting 2 DVDs it appears that the only way to install VS 2005 with slipstreamed SP1 is to copy all files to hard drive and run from there (Windows Installer mysteriously doesn't check volume label of HDD).
Is it so hard to use small tag files (e.g., "vs2005.cd1", "vs2005.cd2") instead of volume label checks?
Windows Installer verifies the volume name for removable volumes. This is documented for the Media table at http://msdn2.microsoft.com/en-us/library/aa369801.aspx.
I ran into the same problem, which apparently makes it impossible to slipstream Visual Studio from CDs onto a DVD. What the reasoning behind requiring a specific volume name? You should be able to determine if the disk is correct from its contents. At the very least, please make an incorrect label be a warning you can choose to ignore.
Also, when is Microsoft going to release a fully integrated package (Visual Studio + SP1 + Vista Update)? This would make it much easier for us developers, and you would be able to repackage the files so both Visual Studio and MSDN can fit on the same DVD.
when is Microsoft going to release a fully integrated package (Visual Studio + SP1 + Vista Update)?
Gets worse - latest MSDN disk 3070.1 VS2005 Pro Edition has same problem so not possible to install VS2005 - dosent anyone test anything at MS anymore!!!!
Since Visual Studio is modular, you can install multiple SKUs on top of each other. You may run across