- Files to install
- For a network setup
- WINDEV framework
- Setup mode of the framework
- Downloading the framework
- Framework location
- Properties of files to install
- "Path" tab
- "Shortcuts" tab
- "Version" tab
- "Options" tab
- "HFSQL" tab (for the executables and the data files only)
- "Framework" tab (for the executables only)
Selecting the files to install and the framework of the installer
The setup wizard allows you to:
One of the main steps when creating a setup is the selection of the files to install.
By default, the setup program automatically selects all the files found in the EXE sub-directory of your project excluding the data files (".FIC", ".NDX", ".MMO"). The selected files will be installed on the user computers.
The files displayed in green correspond to the new files to install since the last setup generation.
To add files to install, click the "Add" button and select the files to add.
To delete files from the setup, select the file and click the "Remove" button.
To configure the setup properties of each file
, select the file and click the "Properties" button. You have the ability to create a shortcut with a command line for one or more files, manage the file versions when updating the application, manage the automatic data modification, ... For more details, see Properties of files
Remark: From version 19, HFSQL is the new name of HyperFileSQL.
For a network setup
When performing a network setup, the setup program creation wizard allows you to choose the computer on which each file must be installed. Each file can be installed:
- on the server only (data files shared by all the users for example).
- on the user computers only (the executable of the application for example).
- both on the server and on the user computers (a ".INI" file for example, used to configure the application installed on the server with the default parameters and the applications installed on the user computers with parameters specific to the users).
To specify the computers on which each one of the files must be installed, all you have to do is check the box:
- "Server" for the files to install on the server. These files will be installed when the setup program is run on the server.
- "Client" for the files to install on the user computers. These files will be installed when the setup program is run on the user computers.
- "Server" and "Client" for the files to install both on the server and on the user computers.
Setup mode of the framework
The WINDEV framework corresponds to all the WINDEV DLLs. By default, the WINDEV framework is included in the setup program. All the framework elements required for the application to operate are automatically installed with the application.
To create "smaller" setup programs, you can:
- download the WINDEV framework from the PC SOFT site.
- install no framework. The framework installed on the user computers will be used. This framework will be downloaded if it does not exist.
Remark: Downloading the WINDEV framework is possible even if your application is using renamed DLLs.
Downloading the framework
The option "Download the WINDEV framework from the PC SOFT site" is used to create a smaller setup.
If your application contains executables that use a common renamed framework, you have the ability to specify the setup directory of the framework (next step of the wizard). By default, the setup directory is "<srCommonProgramFiles>\ <Company Name> \Framework\".
When installing the application, the user will have to be connected to the Internet. The following window will be displayed as soon as the setup program is started:
Whenever the executable is run, all the files of the WINDEV framework will be automatically downloaded from the PC SOFT site. The version of the downloaded framework will correspond to the WINDEV version that was used to create the executable.
Remark: To translate the different elements found in this window, click the "FTP settings" button and the "Translate" button.
By default, the common framework is installed in the "<Setup directory of elements common to several applications>\PC SOFT\<WINDEV version>\Framework" directory,
- "<Setup directory of elements common to several applications>" corresponds to the directory returned by SysDir (associated with the srCommonProgramFiles constant).
- "<WINDEV version>" corresponds to the WINDEV version that was used to create the executable ("21.0" if the executable was created with WINDEV 21 for example).
Properties of files to install
This tab is used to specify:
- the setup directory of the file. The following shortcuts 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.
- <WinDir>: Windows directory of user computers
- <SetupFile>: setup directory of data files. The setup program creation wizard allows you to configure this directory. See Configuring the directory of data files for more details.
- <srProgramFiles>: "Program Files" directory of the user computers.
- the name of the file installed. By default, the file has the same name. However, a different name can be given to the file during the setup.
This tab is used to create for the selected file:
- a shortcut in the "Start" menu
- and/or a shortcut on the desktop.
- and/or shortcut in the quick launch bar.
To create a shortcut:
- Select the type of shortcut to create.
- Enter the caption of the shortcut in each language supported by the setup program.
- Enter the group of programs where the shortcut must be created.
Remark: This group of programs will be created if it does not exist on the user computer.
- Specify (if necessary) the parameters of the shortcut. The execution of this shortcut will start a command line.
For example, the command line: "C:\MyDirectory\MyApplication.EXE /Login = Bill" contains:
- the full path of the file associated with the shortcut.
In our example: "C:\MyDirectory\MyApplication.EXE".
- the parameters of the shortcut.
In our example: "/Login = Bill".
Remark: By default, for each executable installed, a shortcut will be created:
- in the "Start" menu of the setup computer.
- on the desktop of setup computer.
By default, when updating an application, if files with the same name already exist in the setup directory, these files are replaced (even if the replaced files are more recent than the installed files). No warning window is displayed to confirm these replacements.
To manage the collisions:
- To install the selected file even if a more recent file with the same name is already found in the setup directory, check "Replace the file even if it is more recent".
- To avoid installing the selected files if a file with the same name is found in the setup directory, check "Don't install if the file already exists".
- To ask the user to confirm whether the selected files must be replaced or not, check "Confirm the replacement of the file".
- To rename the existing file, check "Rename the replaced file with the name below", and enter the name and the extension of the replaced file. For example: MyImage_Bak.GIF.
This tab is used to define the setup options and the compression options of the files as well as the group to which the file is associated.
"HFSQL" tab (for the executables and the data files only)
This tab is used to:
- specify whether the automatic data modification is managed.
- manage the existence of files in Hyper File 5.5 format.
If the selected file is an index, you have the ability to remove the index from the setup and to rebuild it automatically during the setup.
"Framework" tab (for the executables only)
This tab is used to specify the mode for using the framework. The information displayed in this tab cannot be modified and it depends on the information specified in the wizard screen. The different possibilities are as follows:
- Don't install the framework for this executable. In this case, if the framework is not installed on the current computer, it will be downloaded by the user.
- Use the common WINDEV framework. Use the common framework installed on the user computer. If this common framework is not installed, it will be downloaded by the user.
- Use the common renamed framework: Use the common renamed framework installed on the user computer. If this framework is not installed, it will be downloaded by the user.
- Use a framework specific to the executable: Use the framework specified when creating the executable.
- Use a framework specific to the executable (renamed DLLs): Use the framework specified when creating the executable.