Microsoft Visual Studio 2005

Version: 8
Views: 3.6k  |  Created: 12/29/2005

Average Rating: 0
Visual Studio 2005 has 1 inventory records, 5 Questions, 0 Blogs and 0 links. Please help add to this by sharing more!

Deployment Tips (10)

Most Common Setup Type
Not Determined
Average Package Difficulty Rating
Rated 5 / 5 (Very Difficult) based on 1 ratings
Most Commonly Reported Deployment Method
Vendor Provided Command Line (switch driven)
or cancel
119
Command Line

"c:\windows\system32\maint\Patches\MSI_Corel_Draw_X3\main\CGS13\setup.msi" SERIALNUMBER=DR13WEX-0242148-NUT /qb

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Note
Procedures
1.-Create an installation point by copying the contents of the Visual Studio Pro 2005 MSDN DVD to a folder/share called VS_PRO_2005 on the network.
*Gotcha*: The path to the installation point cannot be changed after because they are hardcoded inside the INIs that are created during this process (The INI in contained inside the MST file)

2.-Locate a test computer that has the same operating system that you want to deploy Visual Studio to in your network, and make sure that it does not already have Visual Studio 2005 installed.

3.-Install .NET Framework 2.0 on your test computer (required for creating an unattend file)

4.-Copy the following line into a file called CREATE_MST.CMD and launch it to create the MST file.
"%~DP0vs\setup\setup.exe" /CreateTransform="%~DP0VS2005.mst"
Note: The %~DP0 is a variable that stores the path where the CMD file is located. If the CMD file is in G:\VS_PRO_2005 the %~DP0 is a variable will contain G:\VS_PRO_2005\ (Notice the extra backslash)
This %~DP0 does not work at the CMD prompt or in a .BAT file. You can also use UNC paths instead but then the server name cannot be changed, too.

5.-At the root of the VS_PRO_2005 folder create CMD files:
0INSTALL_MSI31.CMD
%~DP0vs\wcu\msi31\WindowsInstaller-KB893803-v2-x86.exe /quiet /norestart

1INSTALL_DOTNET20.CMD
%~DP0vs\wcu\dotNetFramework\dotnetfx.exe /q:a /c:"install /q"

2INSTALL_MSXML6.CMD
%~DP0vs\wcu\MSXML\msxml6.msi /qr REBOOT=RS

3INSTALL_DOCEXP2005.CMD
%~DP0vs\wcu\DExplore\DExplore.exe /q /c:"msiexec /qr /i dexplore.msi ADDEPLOY=1"

INSTALL_VS2005.CMD
MSIEXEC /i %~DP0vs\vs_setup.MSI TRANSFORM=%~DP0vs2005.mst /L*v c:\temp\vs2005.log ALLUSERS=1 ADDEPLOY=1

The following components are *optional* and can be installed anytime after the required components for the platform and Visual Studio are installed. (As per the adminreadme.htm file)

INSTALL_VJ#REDIST20.CMD
%~DP0vs\wcu\JSharpRedistCore\vjredist.exe /q:a /c:"install /q"

INSTALL_MSVS2005_64PREREQ.CMD
%~DP0vs\wcu\64bitPrereq\x64\vs_bsln.exe /Q

INSTALL_MSVS64SDK.CMD
%~DP0vs\wcu\SDK\x64\setup.exe /q:a /c:"install /q"

INSTALL_MDAC28.CMD
::Microsoft Data Access Components v2.8
%~DP0vs\wcu\mdac28\mdac_typ.exe /Q /C:"dasetup /Q /N"


6.-On a machine that does not already have Visual Studio 2005 installed, map the same drive letter that was used to create the MST file.

7.-Run the CMD files in order with a reboot before installing VS2005.


**Gotchas**
-Make sure that you create the INI file on a computer that does NOT already have Visual Studio 2005 installed. If you have VS installed, you will end up creating an INI file for a maintenance mode update instead of an initial install of VS.

-The INI file for VS is unique to each version of VS (such as Pro, Standard, Team System), and also unique to the OS that you want to install on (Windows 2000, Windows XP, etc). Make sure that you create INI files on computers that match what you will eventually be deploying to.

-If you flag all the files in the sharepoint as READ ONLY, you will not be able to generate an MST file. During the creation of the MST file, Setup.exe copies the vs_setup.msi file to the TEMP folder, file attributes and all. Setup.exe then modifies that copy of the MSI to generate the MST file. Therefore the vs_setup.msi file in the sharepoint cannot have the READ ONLY file attribute.


**Failed attempts**
Aaron Stebner's WebLog has his way of installing VS 2005 but the method installs all prerequisites regardless if they are already installed or not. The kicker is that it reboots the machine and you canÂ’t stop it.

M$ has their own “How to deploy Visual Studio 2005 by using Systems Management server” and recommends to use smswrapper.exe to launch Setup.exe. Alas this smswrapper.exe seams to have been created for VS.NET2003 and exits so fast that Task Manager doesn't have time to display it.

The only solution that worked for me comes from the \setup\adminreadme.htm file in VS2005. The method involves installing all the prerequisites and then installing VS2005.

Dec2005
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Note
How to make Microsoft Visual Studio 2005 silently deploy from Altiris (without a reboot.) FWIW: This was quite a fox hunt and took weeks of hunting and testing.

-----------------------------------
Client must meet the following requirementsÂ…
- Windows XP SP2 (Auto update or downloaded.)
- Microsoft Office 2003
- Windows Installer 3.1 (KB89803)
- - - Windows installer comes with Visual Studio 2005 in “vs\wcu\msi31”.


At our company we want all packages to deploy completely to the client and not share directories on the network. (In other words the “VS” and “MSDN” directories need to be copied to the client instead of shared.)

There’s a problem with file and directory lengths in this package so I had to create a .rip file and unpack it on the local client. I chose “c:\vs2005” to start the Rapid Install file.

- Why not use Wise? Wise appears to have a file size limit creating .msi (.exe) files. The VS directory size is 1.17G and the package Wise created had all the directories but didnÂ’t have all the files. Rapid Install worked flawlessly. The MSDN directory doesnÂ’t need to be ripped as there wasnÂ’t an issue with directory length.

To silently deploy Visual Studio 2005 you need to have a vs.ini file which can only be created while setting up the last step. All the commands are as follows.

----------------------------------------------
-3- Microsoft .Net Framework 2.0
\vs\wcu\dotNetFramework\dotnetfx.exe /q:a /c:"install /q"

-4- j#_net_redistributable
\VS\wcu\JSharpRedistCore\vjredist.exe /q:a /c:"install /q"
-5- visual_studio_tools_for_office
\MSDN\wcu\VS Tools for Office\vstor.exe /q:a /c:"install /q"

-6- Microsoft SQL server Express
\VS\wcu\SSE\sqlexpr32.exe -q /norebootchk /qn reboot=ReallySuppress addlocal=all instancename=SQLEXPRESS SCCCHECKLEVEL=IncompatibleComponents:1 SQLAUTOSTART=1 ERRORREPORTING=2 /watsongenman=SQL???.mft ComponentType=3

-7- .Net compact framework
msiexec.exe /i c:\vs2005\vs\wcu\netCF\NetCFSetupv2.msi /qb

-8- Microsoft_device_emulator
\vs\wcu\ARM\vs_emulator.exe /q:a /c:"install /q"

-9- Microsoft_msxml-6.0
msiexec.exe /i c:\vs2005\vs\wcu\msxml\msxml6.msi /qb

-10- Document_Explore
\VS\wcu\DExplore\DExplore.exe /q:a /c:"install /q"

-11- Visual Studio 2005
\vs\setup\setup.exe /unattendfile c:\vs2005\vs.ini REBOOT=ReallySuppress

-----------

-11a- Use the following to create your unattend file.. (vs.ini)
vs\setup\setup.exe createunattend c:\vs2005\vs.ini
This of course needs to be created before running the Visual Studio 2005 command. (-11-)

----------------------------------------------

Create a Sequential task with the first task coping and executing your rip file which creates the “c:\vs2005” directory.

-1- vs05rip.exe /q (creates the “c:\vs2005\” directory on the client)

The next task simply copied the vs.ini file you created to the “c:\vs2005” directory.
-2- copy vs.ini c:\vs2005\ (I used a batch file for this step.)

Then create the resources -3- through -11- and create a Sequential Task to run them. In case itÂ’s not obvious I had to create a batch file to run step -6- as the line was too long for the Altiris Command Line. Set the dependencies to point to the package in front of it and your all good. Fina~Â….
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Note
After reading and rereading the instructions for the enterprise network deployment and SMS deployment from MS as well as the information posted here, I was pretty stumped.

My package was restarting itself partway through the VS install even though ALL of the prerequisites were there. I started to try to disect the ugly unattend.ini file that VS makes and started to see that it was installing the prereqs again! I also noticed a line for each of the installs called InstallActionInteger. Some of these had a value of 1 and some a value of 5. So, I finally had something to Google and discovered that lo, there is a flaw in the unattend process for VS2005!

So, I did a Google search and found this wonderful posting which saved my life. It turns out that MS actually has this more or less documented but personally I've never been able to fathom the correct magic for searching the MS Technet or MSDN sites.

http://blogs.msdn.com/astebner/archive/2006/03/17/554248.aspx

I hope it helps others as well.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Command Line
c:

cd "C:\WINDOWS\system32\Maint\Patches\MSI_Visual_Studios_Dot_Net_2005\VS\wcu\msi31"

WindowsInstaller-KB893803-v2-x86.exe /quiet /norestart

cd "C:\WINDOWS\system32\Maint\Patches\MSI_Visual_Studios_Dot_Net_2005\VS\wcu\dotnetFramework"

dotnetfx.exe /q:a /c:"install /q" /norestart

cd "C:\WINDOWS\system32\Maint\Patches\MSI_Visual_Studios_Dot_Net_2005\VS\"

SQL_Express.exe -a -nr -qm -vb:0

cd C:\WINDOWS\system32\Maint\Patches\MSI_Visual_Studios_Dot_Net_2005\VS\wcu\JSharpRedistCore
vjredist.exe /q:a /c:"install /q" /norestart

cd "C:\WINDOWS\system32\Maint\Patches\MSI_Visual_Studios_Dot_Net_2005\VS\wcu\mdac28"

mdac_typ.exe /Q /C:"dasetup /Q /N"

cd "C:\WINDOWS\system32\Maint\Patches\MSI_Visual_Studios_Dot_Net_2005\VS\wcu\netCF"

NetCFSetupv2.msi /qb /norestart

cd "C:\WINDOWS\system32\Maint\Patches\MSI_Visual_Studios_Dot_Net_2005\VS\wcu\SQLCE"

sqlmobile30devtoolsenu.msi /qb /norestart

cd "C:\WINDOWS\system32\Maint\Patches\MSI_Visual_Studios_Dot_Net_2005\VS\wcu\ARM"

vs_emulator.exe /q:a /c:"install /q" /norestart

cd "C:\WINDOWS\system32\Maint\Patches\MSI_Visual_Studios_Dot_Net_2005\VS\wcu\msxml"

msxml6.msi /qb /norestart

cd "C:\WINDOWS\system32\Maint\Patches\MSI_Visual_Studios_Dot_Net_2005\VS\wcu\DExplorer"

DExplore.exe /q:a /c:"install /q" /norestart

cd "C:\WINDOWS\system32\Maint\Patches\MSI_Visual_Studios_Dot_Net_2005\VS\MSVS2005\VS\wcu\Profiler"

vs_profiler.exe /q:a /c:"install /q" /norestart

cd "C:\WINDOWS\system32\Maint\Patches\MSI_Visual_Studios_Dot_Net_2005\VS\setup\"

setup.exe /unattendfile C:\WINDOWS\system32\Maint\Patches\MSI_Visual_Studios_Dot_Net_2005\VS\vs2005_deployment.ini

Rem Reboot here in command file.

C:\WINDOWS\system32\Maint\Patches\MSI_Visual_Studios_Dot_Net_2005\VS\wcu\msi31\WindowsInstaller-KB893803-v2-x86.exe /quiet /norestart

C:\WINDOWS\system32\Maint\Patches\MSI_Visual_Studios_Dot_Net_2005\dotnetfx\install.exe /q

C:\WINDOWS\system32\Maint\Patches\MSI_Visual_Studios_Dot_Net_2005\VS\wcu\netCF\NetCFSetupv2.msi /qb /norestart

C:\WINDOWS\system32\Maint\Patches\MSI_Visual_Studios_Dot_Net_2005\VS\wcu\msxml\msxml6.msi /qn /norestart

C:\WINDOWS\system32\Maint\Patches\MSI_Visual_Studios_Dot_Net_2005\DExplore\install.exe /q

C:\WINDOWS\system32\Maint\Patches\MSI_Visual_Studios_Dot_Net_2005\VS\wcu\SSE\SQLExpr.exe -q /norebootchk /qn reboot=ReallySuppress addlocal=all instancename=SQLEXPR SCCCHECKLEVEL=IncompatibleComponents:1;MDAC25Version:0 SQLAUTOSTART=1 ERRORREPORTING=2 /watsongenman=SQL???.mft ComponentType=3

C:\WINDOWS\system32\Maint\Patches\MSI_Visual_Studios_Dot_Net_2005\vjredist\install.exe /q

msiexec /i C:\WINDOWS\system32\Maint\Patches\MSI_Visual_Studios_Dot_Net_2005\VS\vs_setup.msi TRANSFORMS=C:\WINDOWS\system32\Maint\Patches\MSI_Visual_Studios_Dot_Net_2005\\msvs2005.mst /norestart

msiexec.exe /qb /i \\massey\disk\ITSlabs\Altiris\Software\MSVS2005\MSDE\msdn.msi SETUP_EXE=yes

REM echo %1\CurrentSettings.vssettings %SystemDrive%\I\Visual Studio 2005\Settings\CurrentSettings.vssettings
copy /Y %1\CurrentSettings.vssettings "%SystemDrive%\I\Visual Studio 2005\Settings"
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Note
Just to expand on Cary's notes:

Make sure you have a "/" in front of the createunattend switch or else it will not work.

See below:

-11a- Use the following to create your unattend file.. (vs.ini)
vs\setup\setup.exe /createunattend c:\vs2005\vs.ini
This of course needs to be created before running the Visual Studio 2005 command. (-11-)
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Note
Installing SP 1.
The download comes in the format of an EXE. Once downloaded run with /extract c:\VS2005SP1. This will extract the .msp from the installer and either you can add this to your msi or deploy afterwards with the relevant msiexec commands
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Note
Procedures
1.-Create an installation point by copying the contents of the Visual Studio Pro 2005 MSDN DVD to a folder/share called VS_PRO_2005 on the network.
*Gotcha*: The path to the installation point cannot be changed after because they are hardcoded inside the INIs that are created during this process (The INI in contained inside the MST file)

2.-Locate a test computer that has the same operating system that you want to deploy Visual Studio to in your network, and make sure that it does not already have Visual Studio 2005 installed.

3.-Install .NET Framework 2.0 on your test computer (required for creating an unattend file)

4.-Copy the following line into a file called CREATE_MST.CMD and launch it to create the MST file.
"%~DP0vs\setup\setup.exe" /CreateTransform="%~DP0VS2005.mst"
Note: The %~DP0 is a variable that stores the path where the CMD file is located. If the CMD file is in G:\VS_PRO_2005 the %~DP0 is a variable will contain G:\VS_PRO_2005\ (Notice the extra backslash)
This %~DP0 does not work at the CMD prompt or in a .BAT file. You can also use UNC paths instead but then the server name cannot be changed, too.

5.-At the root of the VS_PRO_2005 folder create CMD files:
0INSTALL_MSI31.CMD
%~DP0vs\wcu\msi31\WindowsInstaller-KB893803-v2-x86.exe /quiet /norestart

1INSTALL_DOTNET20.CMD
%~DP0vs\wcu\dotNetFramework\dotnetfx.exe /q:a /c:"install /q"

2INSTALL_MSXML6.CMD
%~DP0vs\wcu\MSXML\msxml6.msi /qr REBOOT=RS

3INSTALL_DOCEXP2005.CMD
%~DP0vs\wcu\DExplore\DExplore.exe /q /c:"msiexec /qr /i dexplore.msi ADDEPLOY=1"

INSTALL_VS2005.CMD
MSIEXEC /i %~DP0vs\vs_setup.MSI TRANSFORM=%~DP0vs2005.mst /L*v c:\temp\vs2005.log ALLUSERS=1 ADDEPLOY=1

The following components are *optional* and can be installed anytime after the required components for the platform and Visual Studio are installed. (As per the adminreadme.htm file)

INSTALL_VJ#REDIST20.CMD
%~DP0vs\wcu\JSharpRedistCore\vjredist.exe /q:a /c:"install /q"

INSTALL_MSVS2005_64PREREQ.CMD
%~DP0vs\wcu\64bitPrereq\x64\vs_bsln.exe /Q

INSTALL_MSVS64SDK.CMD
%~DP0vs\wcu\SDK\x64\setup.exe /q:a /c:"install /q"

INSTALL_MDAC28.CMD
::Microsoft Data Access Components v2.8
%~DP0vs\wcu\mdac28\mdac_typ.exe /Q /C:"dasetup /Q /N"


6.-On a machine that does not already have Visual Studio 2005 installed, map the same drive letter that was used to create the MST file.

7.-Run the CMD files in order with a reboot before installing VS2005.


**Gotchas**
-Make sure that you create the INI file on a computer that does NOT already have Visual Studio 2005 installed. If you have VS installed, you will end up creating an INI file for a maintenance mode update instead of an initial install of VS.

-The INI file for VS is unique to each version of VS (such as Pro, Standard, Team System), and also unique to the OS that you want to install on (Windows 2000, Windows XP, etc). Make sure that you create INI files on computers that match what you will eventually be deploying to.

-If you flag all the files in the sharepoint as READ ONLY, you will not be able to generate an MST file. During the creation of the MST file, Setup.exe copies the vs_setup.msi file to the TEMP folder, file attributes and all. Setup.exe then modifies that copy of the MSI to generate the MST file. Therefore the vs_setup.msi file in the sharepoint cannot have the READ ONLY file attribute.


**Failed attempts**
Aaron Stebner's WebLog has his way of installing VS 2005 but the method installs all prerequisites regardless if they are already installed or not. The kicker is that it reboots the machine and you can’t stop it.

M$ has their own “How to deploy Visual Studio 2005 by using Systems Management server” and recommends to use smswrapper.exe to launch Setup.exe. Alas this smswrapper.exe seams to have been created for VS.NET2003 and exits so fast that Task Manager doesn't have time to display it.

The only solution that worked for me comes from the \setup\adminreadme.htm file in VS2005. The method involves installing all the prerequisites and then installing VS2005.

Dec2005
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Note
How to make Microsoft Visual Studio 2005 silently deploy from Altiris (without a reboot.) FWIW: This was quite a fox hunt and took weeks of hunting and testing.

-----------------------------------
Client must meet the following requirements
- Windows XP SP2 (Auto update or downloaded.)
- Microsoft Office 2003
- Windows Installer 3.1 (KB89803)
- - - Windows installer comes with Visual Studio 2005 in “vs\wcu\msi31”.


At our company we want all packages to deploy completely to the client and not share directories on the network. (In other words the “VS” and “MSDN” directories need to be copied to the client instead of shared.)

There’s a problem with file and directory lengths in this package so I had to create a .rip file and unpack it on the local client. I chose “c:\vs2005” to start the Rapid Install file.

- Why not use Wise? Wise appears to have a file size limit creating .msi (.exe) files. The VS directory size is 1.17G and the package Wise created had all the directories but didn’t have all the files. Rapid Install worked flawlessly. The MSDN directory doesn’t need to be ripped as there wasn’t an issue with directory length.

To silently deploy Visual Studio 2005 you need to have a vs.ini file which can only be created while setting up the last step. All the commands are as follows.

----------------------------------------------
-3- Microsoft .Net Framework 2.0
\vs\wcu\dotNetFramework\dotnetfx.exe /q:a /c:"install /q"

-4- j#_net_redistributable
\VS\wcu\JSharpRedistCore\vjredist.exe /q:a /c:"install /q"
-5- visual_studio_tools_for_office
\MSDN\wcu\VS Tools for Office\vstor.exe /q:a /c:"install /q"

-6- Microsoft SQL server Express
\VS\wcu\SSE\sqlexpr32.exe -q /norebootchk /qn reboot=ReallySuppress addlocal=all instancename=SQLEXPRESS SCCCHECKLEVEL=IncompatibleComponents:1 SQLAUTOSTART=1 ERRORREPORTING=2 /watsongenman=SQL???.mft ComponentType=3

-7- .Net compact framework
msiexec.exe /i c:\vs2005\vs\wcu\netCF\NetCFSetupv2.msi /qb

-8- Microsoft_device_emulator
\vs\wcu\ARM\vs_emulator.exe /q:a /c:"install /q"

-9- Microsoft_msxml-6.0
msiexec.exe /i c:\vs2005\vs\wcu\msxml\msxml6.msi /qb

-10- Document_Explore
\VS\wcu\DExplore\DExplore.exe /q:a /c:"install /q"

-11- Visual Studio 2005
\vs\setup\setup.exe /unattendfile c:\vs2005\vs.ini REBOOT=ReallySuppress

-----------

-11a- Use the following to create your unattend file.. (vs.ini)
vs\setup\setup.exe createunattend c:\vs2005\vs.ini
This of course needs to be created before running the Visual Studio 2005 command. (-11-)

----------------------------------------------

Create a Sequential task with the first task coping and executing your rip file which creates the “c:\vs2005” directory.

-1- vs05rip.exe /q (creates the “c:\vs2005\” directory on the client)

The next task simply copied the vs.ini file you created to the “c:\vs2005” directory.
-2- copy vs.ini c:\vs2005\ (I used a batch file for this step.)

Then create the resources -3- through -11- and create a Sequential Task to run them. In case it’s not obvious I had to create a batch file to run step -6- as the line was too long for the Altiris Command Line. Set the dependencies to point to the package in front of it and your all good. Fina~.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
116
Note

If you are having issues installing, please email me at a.mackres@massey.ac.nz

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment

Inventory Records (1)

View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.

Versions

Visual Studio 2005

Version

8

Questions & Answers (5)

Questions & Answers related to Microsoft Visual Studio 2005

1
ANSWERS
5
ANSWERS
1
ANSWERS

Blogs (0)

Blog posts related to Microsoft Visual Studio 2005

Reviews (0)

Reviews related to Microsoft Visual Studio 2005