2 Installing the ADO.NET Data Providers : Performing a Silent Installation

Performing a Silent Installation
The Setup program provides a command-line option for silent installations. The silent installation is useful for system administrators who want to create a batch file to execute multiple identical installations of the data providers.
IMPORTANT: You must use the setup32.exe or setup64.exe file that resides in the Support subdirectory of the installer directory. You cannot use the silent installer commands against the standard product setup.exe file.
To perform a silent installation:
1
From a command-line prompt, change to the directory containing the DataDirect Connect for ADO.NET file setup32.exe or setup64.exe or ensure that this directory is on your path.
NOTE: If you are installing on a 64-bit machine, you must use setup64.exe, even if the data provider needs to be run in 32-bit mode. The installer adds the libraries required for both 32-bit and 64-bit runtimes.
2
setup[32|64].exe /s /v"arguments /qn /l*v path\log"
See “Command-Line Syntax” for an explanation of the syntax rules. See Table 2-1 for an explanation of each command-line parameter. See Table 2-2 for an explanation of the arguments that follow the /v parameter. The tables are followed by specific examples of the command-line syntax.
3
4
Consult the log that is created during the installation (see “The Installation Log File”) to determine whether the installation was successful or why it failed. You must have this log available if you contact Progress DataDirect for customer support.
The log may contain messages pertaining to components that you did not install. If the end of the log file indicates that installation completed successfully, you can ignore the other messages.
Command-Line Syntax
In general, there must be a space between all command-line parameters and between each argument:
setup32.exe /s /v"arguments /qn /l*v path\log"
Do not include a space between /v and " (the double quotation mark that follows it).
Multiple arguments and parameters can be specified between the opening and closing double quotation marks, but each one must be separated by a space. The arguments are case-sensitive.
IMPORTANT: When any of the command-line parameters include a value that contains a space, that value must be preceded and followed by the escape characters \". For example:
INSTALLDIR=\"C:\Program Files\My Providers\"
and
CUSTOMER=\"John Doe\"
Parameters and Arguments
See Table 2-1 for an explanation of each command-line parameter. See Table 2-2 for an explanation of the required and optional arguments that follow the /v parameter.
 
/l*v path\name
 
COMPANYNAME=company name
INSTALLDIR=installation directory
KEY=key value
SERIALNUMBER=serial number value
Silent Installation Examples
Following are command-line examples of some typical installations:
Example 1
This command-line installs an evaluation copy of all 32-bit data providers, creates an installation directory named \Program Files\Progress\DataDirect\ConnectForADO.NET40, and creates a log file named adonet.txt in the temp directory:
setup32.exe /s /v"COMPANYNAME=DataDirect SERIALNUMBER=EVAL KEY=EVAL INSTALLDIR=\"C:\Program Files\Progress\DataDirect\ConnectForADO.NET40\" /qn /l*v \"c:\temp\adonet.txt\""
Example 2
This command-line installs a licensed copy of a 32-bit data provider, creates an installation directory named \Program Files\DataDirect\Connect_for_ADO.NET_40, and creates a log file named adonet40.txt in the "dotnetlog" directory:
setup32.exe /s /v"COMPANYNAME=DataDirect SERIALNUMBER=12345921 KEY=1234567 INSTALLDIR=\"C:\Program Files\Progress\DataDirect\Connect_for_ADO.NET_40\" SAMPLES=FALSE /qn /l*v \"c:\dotnetlog\adonet40.txt\""
Example 3: For Visual Studio 2008 and Visual Studio 2010 Users
NOTE: Close Visual Studio 2008 if it is open before integrating or uninstalling the help.
This command-line integrates the online help for the data providers into Visual Studio 2008, using the installation directory created in Example 2.
Msiexec /install "\Program Files\DataDirect\Connect_for_ADO.NET_40\tools\helpSetup08.msi" /qn
This command-line integrates the online help for the data providers into Visual Studio 2010, using the installation directory created in Example 2.
Msiexec /install "\Program Files\DataDirect\Connect_for_ADO.NET_40\tools\helpSetup10.msi" /qn
This command-line uninstalls the help files that were integrated into Visual Studio 2008. This step should be performed before uninstalling the data provider:
Msiexec /uninstall "\Program Files\DataDirect\Connect_for_ADO.NET_40\tools\helpSetup08.msi" /qn
This command-line uninstalls the help files that were integrated into Visual Studio 2010. This step should be performed before uninstalling the data provider:
Msiexec /uninstall "\Program Files\DataDirect\Connect_for_ADO.NET_40\tools\helpSetup10.msi" /qn
Example 4
This command-line uninstalls the 32-bit data providers, and creates a log file named adonet40_uninstall.txt:
setup32.exe /s /v"REMOVE=ALL /qn /l*v \"c:\temp\adonet40_uninstall.txt\""
The Installation Log File
If you encounter any problems during the installation, you can find details about the problem in the installation log file, adonet40.log.The log file is located by default in your temporary directory (for example, C:\Documents and Settings\user name\Local Settings\Temp).
You can read the file with a text editor or word processor. Although the file can be very long, the most important information is at the beginning and end. The final lines of the log file indicate whether the installation was successful. Progress DataDirect provides customer support to help you interpret the log file if you encounter problems.
For a silent installation, the initial lines reproduce all of the command-line arguments that you entered. If there was a failure, check the command-line entries closely to see if the syntax is correct.
The log may contain messages pertaining to components that you did not install, or to a version of Visual Studio that is not installed on your machine, for example, Visual Studio 2008 if your machine has only Visual Studio 2010 (or vice versa). If the end of the log file indicates that installation completed successfully, you can ignore the other messages.