Jump to content

Visual Studio Team System 2008 issue


Recommended Posts

Hi to all.

I have Visual Studio Team System 2008 Team Suite evaluation DVD ISO image and Visual Studio 2008 SP1 ISO image with me. I came to know that, due to some reasons slip-streaming of VS 2008 and VS 2008 SP1 is difficult. So, i would like to automate the installation of Visual Studio 2008 and VS 2008 SP1 at same time. For this i need to write a batch file. I would like to have that batch file. Please any one if possible, just post here the batch file according to below mentioned specifications.

To automate the installation of VS 2008 and VS 2008 SP1, i need to put VS 2008 installation setup files and VS 2008 SP1 in same DVD ISO image. But this is not possible due to their size. These two products setup files reach above 4.7 GB limit. So to overcome this, i need to copy contents of SP1 ISO to a folder named VS2008SP1 and later, this folder is converted to zip format. this zip file should be in VS 2008 DVD or VS 2008 ISO image.

The installation should start from VS 2008 setup file. After completion of VS 2008 installation The VS 2008 setup file should be closed. Now the VS 2008 SP1 zip file extraction should start and this uncompressed folder should be placed in any of drives which is having sufficient storage space. Now the installation should start from SP1 setup file. After completion of installation, the extracted folder should be deleted.

Please any one post here the batch file for above said process.


Link to comment
Share on other sites

Perhaps create an administrative install point of both and/or use a transform (mst) file?

msiexec options:

Windows ® Installer. V 5.0.7600.16385 

msiexec /Option <Required Parameter> [Optional Parameter]

Install Options
</package | /i> <Product.msi>
Installs or configures a product
/a <Product.msi>
Administrative install - Installs a product on the network
/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
Advertises a product - m to all users, u to current user
</uninstall | /x> <Product.msi | ProductCode>
Uninstalls the product
Display Options
Quiet mode, no user interaction
Unattended mode - progress bar only
Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI (default)
Help information
Restart Options
Do not restart after the installation is complete
Prompts the user for restart if necessary
Always restart the computer after installation
Logging Options
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
i - Status messages
w - Nonfatal warnings
e - All error messages
a - Start up of actions
r - Action-specific records
u - User requests
c - Initial UI parameters
m - Out-of-memory or fatal exit information
o - Out-of-disk-space messages
p - Terminal properties
v - Verbose output
x - Extra debugging information
+ - Append to existing log file
! - Flush each line to the log
* - Log all information, except for v and x options
/log <LogFile>
Equivalent of /l* <LogFile>
Update Options
/update <Update1.msp>[;Update2.msp]
Applies update(s)
/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi | ProductCode>
Remove update(s) for a product
Repair Options
/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
Repairs a product
p - only if file is missing
o - if file is missing or an older version is installed (default)
e - if file is missing or an equal or older version is installed
d - if file is missing or a different version is installed
c - if file is missing or checksum does not match the calculated value
a - forces all files to be reinstalled
u - all required user-specific registry entries (default)
m - all required computer-specific registry entries (default)
s - all existing shortcuts (default)
v - runs from source and recaches local package
Setting Public Properties

Consult the Windows ® Installer SDK for additional documentation on the
command line syntax.

Copyright © Microsoft Corporation. All rights reserved.
Portions of this software are based in part on the work of the Independent JPEG Group.

Link to comment
Share on other sites

It's actually well-known that VS 2008 just can't be slipstreamed in any supportable way (see here). In fact, even file replacement seems to break installs, meaning you have to script it. There are some workarounds posted (like this one), but they tend to not be 100% reliable - for example, the resulting installation from this method worked on my XP workstation with SP3, but it did not work properly on my Vista SP2 or Win7 box at all. For my own unattended installations, I simply install the prereqs for VS 2008, do a custom install of VS 2008, then install SP1 unattended (setup.exe /q /full).

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Create New...