Visual Studio .Net 2003 full installation
hi folks, i have just been given visual studio .net 2003 to package.
as if that wasnt bad enough, the client want everthing installed...ahhhh nightmare!
after reading a couple of articles here, i see that people dont extract the embedded msi's, they simply create a command line to install.
Is this the best\only solution?
any tips and tricks are much appreciated
as if that wasnt bad enough, the client want everthing installed...ahhhh nightmare!
after reading a couple of articles here, i see that people dont extract the embedded msi's, they simply create a command line to install.
Is this the best\only solution?
any tips and tricks are much appreciated
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
joe_virani
17 years ago
I have the same project and my client only want visual c# and vb.net installed.
Installing everything is easy just run the command below and make sure your source files are all in one folder.You will have to run the install and supply the missing files from the cd 2 and 3. run
for the prereqs;
msiexec /i weccom.msi /qB
msiexec /i bootstrap.msi /qB
msiexec /i jsredis1.msi /qb
msiexec /i netfx.msi ALLUSERS=1 /qb
(may want to add the allusers to all of them after determing what prereqs are required for your xp image)
app install;
msiexec /qb- /i \\server\vs2003\vs_setup.msi ALLUSERS=1 TRANSFORMS="full path to transform file" VSEXTUI=1 PIDKEY="your license key" ADDLOCAL="ALL"
VSEXTUI=1 this tricks the MSI into thinking it is being run from SETUP.EXE.
PIDKEY set this property to your license number without any dashes
ADDLOCAL this determines what features are installed locally. I got this very long list from running the SETUP.EXe with verbose MSI logging turned on in the registry and looking at the installation log file in my %TEMP% directory. See below for an example that installs everything but the web development tools.
later
Joe Virani
Houston , Texas
Installing everything is easy just run the command below and make sure your source files are all in one folder.You will have to run the install and supply the missing files from the cd 2 and 3. run
for the prereqs;
msiexec /i weccom.msi /qB
msiexec /i bootstrap.msi /qB
msiexec /i jsredis1.msi /qb
msiexec /i netfx.msi ALLUSERS=1 /qb
(may want to add the allusers to all of them after determing what prereqs are required for your xp image)
app install;
msiexec /qb- /i \\server\vs2003\vs_setup.msi ALLUSERS=1 TRANSFORMS="full path to transform file" VSEXTUI=1 PIDKEY="your license key" ADDLOCAL="ALL"
VSEXTUI=1 this tricks the MSI into thinking it is being run from SETUP.EXE.
PIDKEY set this property to your license number without any dashes
ADDLOCAL this determines what features are installed locally. I got this very long list from running the SETUP.EXe with verbose MSI logging turned on in the registry and looking at the installation log file in my %TEMP% directory. See below for an example that installs everything but the web development tools.
later
Joe Virani
Houston , Texas
Posted by:
ibi
17 years ago
ORIGINAL: joe_virani
VSEXTUI=1 this tricks the MSI into thinking it is being run from SETUP.EXE.
PIDKEY set this property to your license number without any dashes
ADDLOCAL this determines what features are installed locally. I got this very long list from running the SETUP.EXe with verbose MSI logging turned on in the registry and looking at the installation log file in my %TEMP% directory. See below for an example that installs everything but the web development tools.
hi joe,
that might not be enough. i've experienced that you have to provide another property called SETUPWINDOW.
i've written a complete guide on that and posted it at VS2003 Silent on DoctorDeploy
take care,
http://www.doctordeploy.com
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.