PC SOFT

ONLINE HELP
 WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English EN
  • Overview
  • Basic setting
  • Default path of setup on the end-user computer
  • Default path of reference setup (network setup only)
  • Advanced setting of setup directory
  • Allow the user to save the replaced files
  • Run a program at the end of setup
  • Configure a silent setup
  • Modify the identifier used to uninstall the application
  • Modify or create the "AutoExec.BAT" file
  • Modify or create the ".INI" files
  • Modify or create values in the registry
  • Implementing the UAC for the installer
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac CatalystUniversal Windows 10 App
Others
Stored procedures
Overview
The setup creation wizard allows you to specify the setup directory.
In the "Setup directory" step of wizard, you have the ability to specify:
Basic setting

Default path of setup on the end-user computer

The setup configuration is used to select the setup directory proposed by default. The user will be able to modify this directory when installing the application.
This directory is "C:\Program Files\<ApplicationName>" by default.
Versions 19 and later

Default path of reference setup (network setup only)

The setup configuration is used to select the setup directory of reference setup proposed by default. The user will be able to modify this directory when installing the application.
This path is optional.
New in version 19

Default path of reference setup (network setup only)

The setup configuration is used to select the setup directory of reference setup proposed by default. The user will be able to modify this directory when installing the application.
This path is optional.

Default path of reference setup (network setup only)

The setup configuration is used to select the setup directory of reference setup proposed by default. The user will be able to modify this directory when installing the application.
This path is optional.
Advanced setting of setup directory
To access the advanced setting regarding the setup of your application, click the "Advanced" button.
These advanced parameters are used to:

Allow the user to save the replaced files

When updating an application, an additional plane can be included in the setup program. This additional plane allows the user to save the replaced files in a backup directory. This backup directory will be named "Backup_<BackupDate>_<BackupTime>" by default.
Backup of replaced files
This backup can be used if the setup fails for example. To use this backup, the user will have to copy the files found in the backup directory into the setup directory of application.
The backup of replaced files is proposed by default to the users.

Run a program at the end of setup

By default, the setup program proposes to the user to run the application executable at the end of setup. The option "Start the program" is checked. The executable is automatically run when clicking the "Done" button.
The setup program creation wizard allows you to specify the executable that must be run and to associate parameters with this executable. Only an executable (".EXE" file) can be run.
The executable to run corresponds to:
  • the name and full path of the executable file. The following keywords can be used:
    • <SetupDir>: setup directory chosen by the user during the setup.
    • <SetupDrive>: drive of the setup directory chosen by the user during the setup.
    • <SetupFile>: setup directory of data files. The setup program creation wizard allows you to configure this directory. For more details, see Configuring the directory of data files.
    • <WinDir>: Windows directory of user computers
    • <SysDir>: system directory.
    • <RefDir>: reference directory for the setups with automatic update only.
  • the runtime parameters of the program installed (if necessary).
For example: "<SetupDir>\MyApp.EXE /Param".
Remark: If modifications are performed in the "AutoExec.Bat" file, no program should be run at the end of the setup. Indeed, the modifications performed in this file will be taken into account when the computer is restarted.
Versions 23 and later

Configure a silent setup

The setups of reference version and client version can be performed in silent mode. In this case, the setup will be done without any user intervention. The options defined by default will be automatically used.
The available options are:
  • Silent client setup: the application setup for the end user does not require any user action.
  • Silent deployment of reference version (available during a setup with automatic update): the reference version of network setup will be installed without any user intervention.
New in version 23

Configure a silent setup

The setups of reference version and client version can be performed in silent mode. In this case, the setup will be done without any user intervention. The options defined by default will be automatically used.
The available options are:
  • Silent client setup: the application setup for the end user does not require any user action.
  • Silent deployment of reference version (available during a setup with automatic update): the reference version of network setup will be installed without any user intervention.

Configure a silent setup

The setups of reference version and client version can be performed in silent mode. In this case, the setup will be done without any user intervention. The options defined by default will be automatically used.
The available options are:
  • Silent client setup: the application setup for the end user does not require any user action.
  • Silent deployment of reference version (available during a setup with automatic update): the reference version of network setup will be installed without any user intervention.

Modify the identifier used to uninstall the application

If you have chosen to allow your application to be uninstalled, a specific identifier is automatically created in the registry. This identifier can be modified via the setup program creation wizard.
By default, this identifier is "<ApplicationNameWithoutSpace>". For example, "WDCustomer" for the "WD Customer" application. This identifier may (or may not) contain space characters.
This identifier will be created in the key:
  • "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Uninstall" in Windows 2000 and NT.
  • "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall" in Windows 98 and Me.

Modify or create the "AutoExec.BAT" file

You have the ability to modify or create the "AutoExec.BAT" file on the setup computers. This file will be modified or created (if necessary) when the computer is restarted. In this case, a reboot is automatically proposed at the end of the application setup.
The "AutoExec.BAT" file is used to:
  • add the directory of the application executable into the PATH.
  • start the application when starting the setup computer.
  • ...
Reminders:
  • The "AutoExec.BAT" file is automatically run when the computer is started.
  • The PATH lists the directories in which the executables (".EXE" files) and the libraries ("DLL" files) are sought in priority.

Modify or create the ".INI" files

When installing a WINDEV application, you have the ability to modify or create the ".INI" files on the setup computers. These files will be associated with the application installed.
The ".INI" files are used to:
  • customize the application according to the connected user.
  • define the default parameters of the application.
  • ...
Then, the ".INI" files can be read and modify from the application directly (INIRead and INIWrite).
Example of modification
For example, to save the setup program runtime language to the "MyAppli.INI" file (in the application setup directory):
  • ".INI" file: <SetupDir>\MyApp.INI
  • Section: LANGUAGE
  • Parameter: LANGUAGE_INSTALL
  • Value: <Language>
The <Language> keyword will be automatically replaced during the setup by the number of the runtime language of the setup program (this number can be used by Nation).
In this example, if the number of the runtime language is 3, the following parameter will be added into the "MyApp.INI" file:
[LANGUAGE]
LANGUAGE_INSTALL=3

Modify or create values in the registry

When installing a WINDEV application, you have the ability to modify or create entries in the registry.
The registry alloows you to:
  • customize the application according to the connected user.
  • define the default parameters of the application.
  • ...
Then the registry can be read and modified from the application directly (RegistrySetValue, RegistryQueryValue, ...).
Example of modification
For example, to save the runtime language of the setup program in the registry, type:
  • Key: HKEY_LOCAL_MACHINE\Software\MyCompany\MyApp\1.0\
  • Name: Language
  • Value: <Language>
The <Language> keyword will be automatically replaced during the setup by the number of the runtime language of the setup program (this number can be used by Nation).
Implementing the UAC for the installer
Versions 20 and later
By default, installing a WINDEV application triggers the UAC.
To access the setting regarding the implementation of UAC, click the "Implementing the UAC" button.
The window that is displayed allows you to modify this operating mode via "The installer DOES NOT require the administrator rights":
  • for the individual setups: the UAC is disabled for the setup on the end-user computer.
  • for the network setups with automatic update. In this case, the UAC can be disabled:
    • for the installer of the end user,
    • for the installer of the reference version,
    • for both.
Caution: The option "Does not require the administrator rights" involves some limitations: no files can be installed in the system directories (Program Files, Windows...), no system files and parameters can be modified (win.ini, path, etc.).
The setup will fail if the rights are not sufficient. Whenever possible, the setup wizard will guide the user in his choices so that he can install the application.
Remark: The implementation of the UAC for the installer can also be configured in the advanced options of the installer. These options are accessible in the "Medium" step of the setup creation wizard.
New in version 20
By default, installing a WINDEV application triggers the UAC.
To access the setting regarding the implementation of UAC, click the "Implementing the UAC" button.
The window that is displayed allows you to modify this operating mode via "The installer DOES NOT require the administrator rights":
  • for the individual setups: the UAC is disabled for the setup on the end-user computer.
  • for the network setups with automatic update. In this case, the UAC can be disabled:
    • for the installer of the end user,
    • for the installer of the reference version,
    • for both.
Caution: The option "Does not require the administrator rights" involves some limitations: no files can be installed in the system directories (Program Files, Windows...), no system files and parameters can be modified (win.ini, path, etc.).
The setup will fail if the rights are not sufficient. Whenever possible, the setup wizard will guide the user in his choices so that he can install the application.
Remark: The implementation of the UAC for the installer can also be configured in the advanced options of the installer. These options are accessible in the "Medium" step of the setup creation wizard.
By default, installing a WINDEV application triggers the UAC.
To access the setting regarding the implementation of UAC, click the "Implementing the UAC" button.
The window that is displayed allows you to modify this operating mode via "The installer DOES NOT require the administrator rights":
  • for the individual setups: the UAC is disabled for the setup on the end-user computer.
  • for the network setups with automatic update. In this case, the UAC can be disabled:
    • for the installer of the end user,
    • for the installer of the reference version,
    • for both.
Caution: The option "Does not require the administrator rights" involves some limitations: no files can be installed in the system directories (Program Files, Windows...), no system files and parameters can be modified (win.ini, path, etc.).
The setup will fail if the rights are not sufficient. Whenever possible, the setup wizard will guide the user in his choices so that he can install the application.
Remark: The implementation of the UAC for the installer can also be configured in the advanced options of the installer. These options are accessible in the "Medium" step of the setup creation wizard.
See also
Minimum version required
  • Version 11
Comments
Click [Add] to post a comment