PC SOFT

WINDEVWEBDEV AND WINDEV MOBILE
ONLINE HELP

Home | Sign in | English UK
  • Overview
  • How to proceed?
  • To create a WINDEV executable
  • To create a WINDEV executable
  • Error case
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
Overview
When your WINDEV application is entirely described (windows, reports, queries, ...), you must create the corresponding executable program:
The executable program (".EXE" file) can be run directly: there is no need to start the application from WINDEV or WINDEV Mobile.
When the executable is created, the application can be deployed on the end-user computers by creating the setup program. For more details, see:
Versions 22 and later
WINDEV Note: The executables created with WINDEV can be checked by the Kit for certification of Windows applications ("Windows App Certification Kit"). The Kit for certification of Windows applications allows you to check your application and to find out whether it is ready to get its certification and its referencing in Windows Store.
New in version 22
WINDEV Note: The executables created with WINDEV can be checked by the Kit for certification of Windows applications ("Windows App Certification Kit"). The Kit for certification of Windows applications allows you to check your application and to find out whether it is ready to get its certification and its referencing in Windows Store.
WINDEV Note: The executables created with WINDEV can be checked by the Kit for certification of Windows applications ("Windows App Certification Kit"). The Kit for certification of Windows applications allows you to check your application and to find out whether it is ready to get its certification and its referencing in Windows Store.
How to proceed?
WINDEVWindows

To create a WINDEV executable

  1. Start the wizard for generating the executable via one of the following methods:
    • Select "Workshop .. Executable .. Generate the Windows executable (32 bits)".
    • Click the executable icon in the toolbar.
    Start the wizard for generating the executable via one of the following methods:
    • On the "Project" pane, in the "Generation" group, click "Generate".
    • Expand executable generation among the quick access buttons and select "Generate the Windows 32-bit executable (exe)".
  2. The wizard informs you whether automatic tests are found or not. If automatic tests are available, the wizard displays the validation rate of project. You can see the details of tests ("Details" button) or cancel the wizard and re-run all the tests ("Cancel and run the tests" button).
  3. Specify the general options of executable (executable name, icon of executable program, ...).
  4. Select:
  5. Enter the error message that will be displayed if a programming error occurs. This error message can be typed in all languages supported by the current project.
  6. Specify whether the input of User Macro-Code is allowed in your application. See Management of UMC for more details.
  7. Specify whether the updates via Patch must be taken into account by the executable. In this case, all you have to do is copy the file corresponding to the patch into the executable directory. See Application patch for more details.
  8. Specify the languages found in the executable.
  9. Specify (if necessary) the files to include in the main library of application.
  10. If your project is using external components, specify whether these external components must be included in the executable.
  11. If your application supports the user groupware, specify the directory for creating the data files of user groupware.
  12. Specify the directory for creating the data files used by the application.
  13. Specify the executable information visible in the "Version" tab or in the "Details" tab of file description in the explorer:
    • Information about the executable (application description, copyright, ...).
    • Versions 16 and later
      Signature of the executable: If the executable must be signed, specify the certificate to use. This certificate must be found in the Windows store (more precisely in the user store and not in the computer store). The signature standard used is PKCS7.
      This signature is used to:
      • make sure that the executable was not modified since its generation.
      • display the editor name in the Windows download window.
      New in version 16
      Signature of the executable: If the executable must be signed, specify the certificate to use. This certificate must be found in the Windows store (more precisely in the user store and not in the computer store). The signature standard used is PKCS7.
      This signature is used to:
      • make sure that the executable was not modified since its generation.
      • display the editor name in the Windows download window.
      Signature of the executable: If the executable must be signed, specify the certificate to use. This certificate must be found in the Windows store (more precisely in the user store and not in the computer store). The signature standard used is PKCS7.
      This signature is used to:
      • make sure that the executable was not modified since its generation.
      • display the editor name in the Windows download window.
  14. Specify the information about the executable version.
  15. Select the mode for using the WINDEV framework (.DLL files). Specify whether the DLLs of the WINDEV framework must be included (or not) in the executable. Select (if necessary) the DLLs that will be used.
  16. If your application is used on Windows Vista (or later), specify whether a manifest must be included in the executable. In this case, specify the level of privilege that must be managed.
  17. Select the external libraries (".WDL" files) used by the executable program.
  18. Validate the creation of the executable program. Once the executable program is created, WINDEV proposes to run this executable.
Note: If the executable and the setup procedure are created at the same time, the wizard also proposes to document the new features.
WINDEVWindows

To create a WINDEV executable

  1. Start the wizard for generating the executable via one of the following methods:
    • On the "Project" pane, in the "Generation" group, click "Generate".
    • Expand Executable generation among the quick access buttons and select "Generate the Windows 32-bit executable (exe)".
  2. Specify the general options of executable (executable name, icon of executable program, ...).
  3. Select:
  4. Enter the error message that will be displayed if a programming error occurs. This error message can be typed in all languages supported by the current project.
  5. Versions 21 and later
    Specify whether the application must send data for the telemetry.
    Caution: implementing the telemetry in an application requires to implement a telemetry server. See the following pages for more details:
    New in version 21
    Specify whether the application must send data for the telemetry.
    Caution: implementing the telemetry in an application requires to implement a telemetry server. See the following pages for more details:
    Specify whether the application must send data for the telemetry.
    Caution: implementing the telemetry in an application requires to implement a telemetry server. See the following pages for more details:
  6. Specify whether the updates via Patch must be taken into account by the executable. In this case, all you have to do is copy the file corresponding to the patch into the executable directory. See Application patch for more details.
  7. Specify the languages found in the executable.
  8. Specify (if necessary) the files to include in the main library of the application.
  9. If your project is using external components, specify whether these external components must be included in the executable.
  10. If your application supports the user groupware, specify the directory for creating the data files of user groupware.
  11. Specify the directory for creating the data files used by the application.
  12. Specify the executable information visible in the "Version" tab or in the "Details" tab of file description in the explorer:
    • Information about the executable (application description, copyright, ...).
    • Versions 16 and later
      Signature of the executable: If the executable must be signed, specify the certificate to use. This certificate must be found in the Windows store (more precisely in the user store and not in the computer store). The signature standard used is PKCS7.
      This signature is used to:
      • make sure that the executable was not modified since its generation.
      • display the editor name in the Windows download window.
      New in version 16
      Signature of the executable: If the executable must be signed, specify the certificate to use. This certificate must be found in the Windows store (more precisely in the user store and not in the computer store). The signature standard used is PKCS7.
      This signature is used to:
      • make sure that the executable was not modified since its generation.
      • display the editor name in the Windows download window.
      Signature of the executable: If the executable must be signed, specify the certificate to use. This certificate must be found in the Windows store (more precisely in the user store and not in the computer store). The signature standard used is PKCS7.
      This signature is used to:
      • make sure that the executable was not modified since its generation.
      • display the editor name in the Windows download window.
  13. Specify the information about the executable version.
  14. Select the mode for using the WINDEV framework (.DLL files). Specify whether the DLLs of the WINDEV framework must be included (or not) in the executable. Select (if necessary) the DLLs that will be used.
  15. If your application is used on Windows Vista (or later), specify whether a manifest must be included in the executable. In this case, specify the level of privilege that must be managed.
  16. Select the external libraries (".WDL" files) used by the executable program.
  17. Validate the creation of the executable program. Once the executable program is created, WINDEV proposes to run this executable.
Note: If the executable and the setup procedure are created at the same time, the wizard also proposes to document the new features.
Error case
If an "Access denied" error occurs during the generation of the executable, it means that a process is blocking this executable.
The blocking program must then be identified. The programs to be examined are those configured to have an impact on all the files found on the disks (backup, data synchronization, antivirus, etc.). A tool such as "Process Explorer" can guide your searches .
Minimum version required
  • Version 9
This page is also available for…
Comments
Click [Add] to post a comment