Installation parameters allow you to indicate specific actions to be executed as part of the version management process. For example, registering a file, placing a file in the System directory on the local drive, or showing the user a "Read-Me" file.
Installation parameters are specified in the .rsp and .rsq files.
More than one parameter can be included for each .rsp and .rsq entry, but only one parameter of each type (Conversion, Default Dialog Response, Location, Operation) can be used. The parameter must be enclosed in angle brackets and separated from the rest of the response file entry by one or more commas, spaces, or tabs.
File names in a BSS are limited to the 8.3 naming convention. A Conversion parameter converts file names back to their long format.
| Parameter | Description | |
|---|---|---|
|
<LONGNAME> |
This parameter converts the file’s 8.3 name in the BSS to the long name specified by the parameter. The localized file will have the long name. Example use of this parameter:
|
Default Dialog Response parameters enable the Version Manager to respond to dialog boxes that might appear during the localization process. This can simplify the version management process for the user by reducing the number of dialog boxes that require a response. These parameters are not case sensitive.
| Parameter | Description |
|---|---|
|
<INUSENOMSG> |
This parameter prevents the Version Manager from displaying a message when it fails to localize a file because the file is “read-only” or the local file is currently in use. This parameter is useful for certain system and MFC DLLs. |
A Location parameter can be used in lieu of a path for common Microsoft Windows directories. These parameters are not case sensitive.
| Parameter | Description |
|---|---|
|
<WINDOWS> |
This parameter localizes files to the current base directory from which Windows is running (For example, C:\Windows). |
|
<SYSTEM> |
This parameter localizes file to the current Windows System directory (For example, C:\Windows\System). |
|
<TEMP> |
This parameter localizes files to the directory specified in the TEMP (or TMP) environment variable. If no such variable is defined, the parameter localizes files to <Drive>:\Temp, where <Drive> represents the drive letter from which the Version Manager is run. |
Operation parameters instruct the Version Manager to perform a specific operation on the associated file after localization has been performed. These parameters are case sensitive.
| Parameter | Description | |
|---|---|---|
|
<ARCHITECTURE_TYPE=x86> |
This parameter specifies the version(s) of regasm to run. See <REGASM> below. |
|
|
<CREATENEW> |
This parameter downloads file only if it doesn’t exist on the local drive. |
|
|
<DOT_NET_REQ=n.n.n> |
This parameter enables a user to specify the required version of the Microsoft .NET Framework. The required version is a prerequisite for successful installation. If the required version is not found, the install fails. Specify the appropriate version in the parameter, for example, 4.5.2 etc., in accordance with the CygNet System Requirements document. |
|
|
<DOWNLOAD_AS=> |
This parameter controls how a file is named when it is transferred from the APPS service to the local file system. Used when the original file name is too long to fit in the BSS file name field. Example use of this parameter:
|
|
|
<GACINSTALL> |
This parameter supports the registration of select items. It triggers special behavior in the CygNet Client Installer and enables CygNet to register a new assembly in the Windows Global Assembly Cache (GAC). Note: This parameter must be combined with one of the <DOT_NET_REQ=n.n.n> parameters above. |
|
|
<REGASM> |
This parameter supports the registration of a C# assembly. Adding the parameter in an .rsq file will run the Microsoft .NET Framework Assembly Registration utility (regasm.exe) against the associated file, which allows COM-based clients to create .NET Framework classes transparently. |
|
|
<REGISTER> |
Use this parameter with COM-based .dll or .ocx files. The parameter instructs the Version Manager to register the file in the Windows Registry by calling the DllRegisterServer() function. This function is assumed to be an exported function of the specified module. |
|
|
<SHELLEXEC:args> |
This parameter attempts to run the specified file or uses the file associations of the local workstation to run the file. Any text included in the optional args (arguments) string is passed to the application as command-line parameters. The colon is required when including arguments. |
|
|
|
