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. Type the command for the installation. The command-line syntax for executing a silent installation is:

   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 Silent Installation Parameters for an explanation of each command-line parameter. See Table Arguments for /v for an explanation of the arguments that follow the /v parameter. The tables are followed by specific examples of the command-line syntax.

3. The installation proceeds without any further user intervention or notification unless you enter an incorrect key, in which case an error is displayed and Setup aborts. You must correct the silent installation command line and execute it again.

4. Consult the log that is created during the installation (see The Installation Log Files) 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 Silent Installation Parameters for an explanation of each command-line parameter. See Table Arguments for /v for an explanation of the required and optional arguments that follow the /v parameter.

Silent Installation Parameters

Arguments for /v

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 C:\Program Files\Progress\DataDirect\ConnectForADO.NET43, 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.NET43\" /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_43, and creates a log file named adonet41.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_43\" /qn /l*v \"c:\dotnetlog\adonet43.txt\""

Example 3: For Visual Studio 2015 and Visual Studio 2017 Users

Note: Close Visual Studio 2015 if it is open before integrating or uninstalling the help.

This command-line integrates the online help for the data providers into Visual Studio 2015, using the installation directory created in Example 2.

"%ProgramFiles(x86)%\Microsoft Help Viewer\v2.2\HlpCtntMgr.exe" /operation install /catalogName "VisualStudio14" /locale en-US /silent /sourceUri "<install_dir>\Help\VS_Help\HelpContentSetup.msha"

This command-line integrates the online help for the data providers into Visual Studio 2017, using the installation directory created in Example 2.

"%ProgramFiles(x86)%\Microsoft Help Viewer\v2.3\HlpCtntMgr.exe" /operation install /catalogName "VisualStudio15" /locale en-US /sourceUri "<install_dir>\Help\VS_Help\helpcontentsetup.msha"

This command-line uninstalls the help files that were integrated into Visual Studio 2015. This step should be performed before uninstalling the data provider:

"%ProgramFiles(x86)%\Microsoft Help Viewer\v2.2\HlpCtntMgr.exe" /operation uninstall /catalogName VisualStudio14 /locale en-US /vendor "Progress DataDirect" /productName "Progress DataDirect Help" /silent /booklist "ADO.NET 4.3 Help"

This command-line uninstalls the help files that were integrated into Visual Studio 2017. This step should be performed before uninstalling the data provider:

"%ProgramFiles(x86)%\Microsoft Help Viewer\v2.3\HlpCtntMgr.exe" /operation uninstall /catalogName VisualStudio15 /locale en-US /vendor "Progress DataDirect" /productName "Progress DataDirect Help" /silent /booklist "ADO.NET 4.3 Help"

Example 4

This command-line uninstalls the 32-bit data providers, and creates a log file named adonet43_uninstall.txt:

setup32.exe /s /v"REMOVE=ALL /qn /l*v \"c:\temp\adonet43_uninstall.txt\""