PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US
  • Overview
  • Framework
  • The different options
  • Using the framework specific to the application
  • Use the common WINDEV framework
  • Using the renamed common WINDEV Framework
  • Describing the framework
  • The different options
  • Use the framework DLLs beside the executable
  • Use the framework included in the executable
  • Use the common framework
  • Options kept for backward compatibility
  • Describing the framework
  • External library
  • External libraries (".WDL" files) used by the executable program
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Others
Stored procedures
Creating an executable: WINDEV framework
Overview
Each WINDEV function is associated with a WINDEV DLL. In order for the executable to operate properly, all the necessary DLLs must be installed with the executable. All these DLLs correspond to the WINDEV Framework.
The wizard for Creating an executable proposes different modes for loading the Framework.
Framework

The different options

WINDEV proposes to:
  • Use the Framework specific to the application.
    In this case, the different framework files may (or may not) be included in the executable.
  • Use the common WINDEV framework.
    In this case, the framework is installed once on the end-user computer, regardless of the number of WINDEV applications used on the computer. Furthermore, this framework can be directly downloaded by the end user.
  • Use the common WINDEV framework and rename it.
    In this case, only the specified framework elements are installed once on the end-user computer, regardless of the number of WINDEV applications used on this computer. This framework can be installed at any location. Furthermore, this framework can be directly downloaded by the end user. This allows you to optimize the memory footprint of your application.

Using the framework specific to the application

This option allows you to customize the WINDEV framework for your application. By default, the wizard for executable creation proposes to load all WINDEV libraries required to run the application. The unnecessary DLLs are not proposed.
Special case: the dynamic compilation
If your application is using the dynamic compilation, you must specify the mode for loading the WINDEV libraries corresponding to the functions used in the dynamic compilation.
Note: To find out the WINDEV library used by a function, see the online help about the relevant function ("Component" paragraph).
Possible choices:
  • Don't include the Framework in the executable: The necessary WINDEV DLLs are automatically copied into the EXE sub-directory of the project when creating the executable.
    If this option is selected, the "Next" button lists the different framework DLLs required to run your application. If your executable is using specific external libraries, the list of libraries is also proposed along with the list of framework DLLs.
  • Include the necessary framework DLLs in the executable: The necessary DLLs will be included in the executable. In this case, the executable size will be increased. When the executable is run for the first time, the different framework DLLs will be extracted from the executable.
    If this option is selected, the "Next" button lists the different framework DLLs required to run your application. If your executable is using specific external libraries, the list of libraries is also proposed along with the list of framework DLLs.
  • Include part of the Framework in the executable: This option is used to select the different DLLs that will be included in the executable. The other DLLs used by the application will be available beside the .EXE file of the application. When the executable is run for the first time, the different framework DLLs included in the executable will be extracted from the executable.
    Click the button and select the WINDEV DLLs to include.
Note: If the WINDEV libraries required by the application and the external libraries are included in the executable, the executable will be stand alone. There is no need to install the libraries and the external libraries on the end-user computers. See Stand-alone executable for more details.
When creating the executable, all the elements of WINDEV framework (loaded during the start or during the first use) will be automatically copied into the "EXE" sub-directory of project.

Use the common WINDEV framework

This option is used to:
  • limit the size of program to install on the end-user computer. Indeed, the WINDEV framework is not copied into the EXE directory of the project and it is not installed on the end-user computer.
  • use the same WINDEV framework for all the WINDEV applications used by the end user. The framework files are only found once on the computer (and not copied with each executable).
Note: This option does not allow you to use renamed DLLs.
If this option is selected, you have the ability to configure the different messages displayed to the end user:
Note: the PC SOFT Framework is available on the end-user computer in the "Program Files\Common files\PC SOFT\23.0\Framework" directory.

Using the renamed common WINDEV Framework

This option is used to:
  • limit the size of program to install on the end-user computer. Indeed, the WINDEV framework is not copied into the EXE directory of the project and it is not installed on the end-user computer.
  • use the same WINDEV framework for all the WINDEV applications used by the end user. The framework files are only found once on the computer (and not copied with each executable).
  • rename the DLLs.
If this option is selected, you have the ability to configure the different messages displayed to the end user.
This option is not available if you are using the XAML or .NET libraries in your application.
Note: When creating the setup, you can choose to supply the framework or ask the end users to download it. You also have the ability to define the setup path of framework.

Describing the framework

For each WINDEV DLL or external library, you can:
  • rename this file ("New name" column). If several WINDEV applications are installed on the same computer, each executable is using its own DLLs.
    The "Prefix" button allows you to replace the "wd190" prefix by the prefix of your choice.
    Note: Don't rename the WINDEV DLLs of programs created with an external language.
  • specify the load mode of this file:
    • when starting the application. In this case, the WINDEV DLL will be available as long as the application is used. However, the time required to start the application may increase according to the number and size of WINDEV DLLs to load. The amount of memory used may also increase.
    • when it is first used (recommended mode). The WINDEV DLL will be loaded in memory only during the first call to a function that is using this library. This load mode is recommended for the DLLs that are rarely used. This load mode optimizes the time required to start the application and the amount of memory used.

Use the framework DLLs beside the executable

The necessary WINDEV DLLs are automatically copied into the EXE sub-directory of the project when creating the executable.
If you select this option:
  • The "Next" button lists the different framework DLLs required to run your application (see Describing the framework).
  • If your executable is using specific external libraries, the list of libraries is also proposed along with the list of framework DLLs.
Versions 20 and later

Use the framework included in the executable

The executable is stand-alone. The DLLs will not be extracted during the start.
If this option is selected, the project is recompiled to check the possible incompatibilities.
Caution: All the framework DLLs are systematically included in the executable. The executable size can be quite important.
Note: The following features are not allowed:
  • Bluetooth functions (feature allowed from version 200051)
  • Native Accesses
  • .NET
  • HTML control in the reports
  • Burn functions (feature allowed from version 200051)
  • Video Conference control
  • CM15 (domotics via USB)
  • Carousel control: image on disk only (feature allowed from version 200051)
  • Xaml control
  • Java functions not available (feature allowed from version 200051)
  • Hasp functions (feature allowed from version 200051)
  • Print in PCL format (feature allowed from version 200051)
  • DirectX 3D charts
  • Management of CAB archives
New in version 20

Use the framework included in the executable

The executable is stand-alone. The DLLs will not be extracted during the start.
If this option is selected, the project is recompiled to check the possible incompatibilities.
Caution: All the framework DLLs are systematically included in the executable. The executable size can be quite important.
Note: The following features are not allowed:
  • Bluetooth functions (feature allowed from version 200051)
  • Native Accesses
  • .NET
  • HTML control in the reports
  • Burn functions (feature allowed from version 200051)
  • Video Conference control
  • CM15 (domotics via USB)
  • Carousel control: image on disk only (feature allowed from version 200051)
  • Xaml control
  • Java functions not available (feature allowed from version 200051)
  • Hasp functions (feature allowed from version 200051)
  • Print in PCL format (feature allowed from version 200051)
  • DirectX 3D charts
  • Management of CAB archives

Use the framework included in the executable

The executable is stand-alone. The DLLs will not be extracted during the start.
If this option is selected, the project is recompiled to check the possible incompatibilities.
Caution: All the framework DLLs are systematically included in the executable. The executable size can be quite important.
Note: The following features are not allowed:
  • Bluetooth functions (feature allowed from version 200051)
  • Native Accesses
  • .NET
  • HTML control in the reports
  • Burn functions (feature allowed from version 200051)
  • Video Conference control
  • CM15 (domotics via USB)
  • Carousel control: image on disk only (feature allowed from version 200051)
  • Xaml control
  • Java functions not available (feature allowed from version 200051)
  • Hasp functions (feature allowed from version 200051)
  • Print in PCL format (feature allowed from version 200051)
  • DirectX 3D charts
  • Management of CAB archives

Use the common framework

This option is used to:
  • limit the size of program to install on the end-user computer. Indeed, the WINDEV framework is not copied into the EXE directory of the project and it is not installed on the end-user computer.
  • use the same WINDEV framework for all the WINDEV applications used by the end user. The framework files are only found once on the computer (and not copied with each executable).
You can:
  • use the common WINDEV Framework: If this option is selected, you have the ability to configure the different messages displayed to the end user:
    Note: the PC SOFT Framework is available on the end-user computer in the "Program Files\Common files\PC SOFT\23.0\Framework" directory.
  • use a renamed framework: This option is not available if you are using the XAML or .NET libraries in your application.
    If this option is selected, the "Next" button lists the different framework DLLs required to run your application. You can select the DLLs, their load mode and the prefix of the new name.
    Note: When creating the setup, you can choose to supply the framework or ask the end users to download it. You also have the ability to define the setup path of framework.

Options kept for backward compatibility

The following options are kept for backward compatibility:
  • Include the necessary framework DLLs in the executable (the DLLs are extracted during the start)
    The necessary DLLs will be included in the executable. In this case, the executable size will be increased. When the executable is run for the first time, the different framework DLLs will be extracted from the executable.
    If you select this option, the "Next" button lists the different framework DLLs required to run your application (see Describing the framework). If your executable is using specific external libraries, the list of libraries is also proposed along with the list of framework DLLs.
  • Include part of the framework in the executable (the DLLs are extracted at startup)
    This option is used to select the different DLLs that will be included in the executable. The other DLLs used by the application will be available beside the .EXE file of the application. When the executable is run for the first time, the different framework DLLs included in the executable will be extracted from the executable.
    Click the button and select the WINDEV DLLs to include.

Describing the framework

For each WINDEV DLL or external library, you can:
  • rename this file ("New name" column). If several WINDEV applications are installed on the same computer, each executable is using its own DLLs.
    The "Prefix" button allows you to replace the "wd190" prefix by the prefix of your choice.
    Note: Don't rename the WINDEV DLLs of programs created with an external language.
  • specify the load mode of this file:
    • when starting the application. In this case, the WINDEV DLL will be available as long as the application is used. However, the time required to start the application may increase according to the number and size of WINDEV DLLs to load. The amount of memory used may also increase.
    • when it is first used (recommended mode). The WINDEV DLL will be loaded in memory only during the first call to a function that is using this library. This load mode is recommended for the DLLs that are rarely used. This load mode optimizes the time required to start the application and the amount of memory used.
External library

External libraries (".WDL" files) used by the executable program

To share resources among several applications, WINDEV allows you to use libraries created by other WINDEV applications. These libraries are called "External libraries". To associate these libraries with the application:
  • select "Workshop .. Library .. External libraries". By default, these libraries will be automatically proposed by the wizard for executable creation.
  • use LoadWDL in your WLanguage code. The external libraries must be supplied along with your application.
Note: See Using several libraries in an application for more details.
For each available external library (".WDL" file), you can:
  • rename this library ("New name"column).
  • include this library in the executable. If the WINDEV libraries required by the application and the external libraries are included in the executable, the executable will be stand alone. There is no need to install the libraries and the external libraries on the end-user computers. See Stand-alone executable for more details.
    Note: If the libraries (".WDL" files) are not included in the executable, the libraries will be automatically copied into the "EXE" sub-directory of the project when creating the executable.
Minimum required version
  • Version 11
Comments
Click [Add] to post a comment