About Windows Installer, the .NET Framework, and Visual Studio.
Now that Visual Studio 2010 SP1 has been released, administrators and developers may wish to install both RTM and SP1 together for a seamless experience. With the release of VS2010 RTM we already published the Visual Studio Administrator Guide that documents a lot of the instructions I’ll utilize below. I encourage you to review that before proceeding with the following instructions, particularly how to avoid restarts during setup by pre-installing certain packages like Windows Installer 4.5 and .NET Framework 4.0.
You’ll create a distribution point that will contain both Visual Studio 2010 RTM and SP1. This will work for existing installations of VS 2010 since setup will simply repair the product if it’s already installed. This has the added benefit that if any files are missing from the target machine, they should be reinstalled without a prompt for source during the SP1 install.
First you’ll be creating copies of the Visual Studio 2010 RTM and SP1 installations that you can share out or install locally.
Next you’ll be creating a batch install that will first install Visual Studio 2010 RTM followed by SP1. You can use any batch or scripting language you like so long as it is already supported on target machines. The example below uses the Windows batch language to make use of tokens like %~dp0 which provides the parent path to the batch script. This is handy in case you change the network or local image location in the future.
"%~dp0setup\setup.exe" /q /norestart
"%~dp0setup\setup.exe" /q /norestart /unattendfile "%~dp0unattend.ini"
"%ProgramFiles%\Microsoft Help Viewer\v1.0\HelpLibManager.exe" /silent /product VS /version 100 /locale en-US /content "%ProgramData%\Microsoft\HelpLibrary" /sourceMedia "%~dp0ProductDocumentation\HelpContentSetup.msha"
"%~dp0SP1\setup.exe" /q /norestart
You might consider adding some error processing for reboot return codes after each command. See the attached batch script for an example.
If you plan on deploying Visual Studio 2010 with SP1 over the network, you can share out the location you created above, ex: <drive>:\VS2010. As noted in the Administrator Guide, spaces in the share path may cause setup to fail so its best you avoid using spaces.
Since the batch file already passes the right options to the installers, the deployment scripts or developers can execute unattend.bat in an elevated command prompt directly.
You’ll use the distribution point you created above to create or modify a package for SCCM to install Visual Studio 2010 RTM and SP1. You’ll follow the process documented in How to: Deploy Visual Studio Using Microsoft System Configuration Manager (SCCM) and add a program to the package after Visual Studio.
The documentation cited above from the Administrators Guide has a number of help links to more information about Active Directory and SCCM.
Why does Microsoft not provide a new ISO with SP1 automatically included? This is so tedious and should be unnecessary.