PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US
  • Overview
  • How to proceed?
  • To create a WINDEV executable
  • To create a WINDEV executable
  • To create a Windows Mobile executable
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 some 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 entered in all the 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 the 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 the 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 name of the editor in the download window of Windows.
      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 name of the editor in the download window of Windows.
      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 name of the editor in the download window of Windows.
  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 entered in all the 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 the 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 name of the editor in the download window of Windows.
      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 name of the editor in the download window of Windows.
      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 name of the editor in the download window of Windows.
  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.
Windows Mobile

To create a Windows Mobile executable

  1. Start the wizard for generating the executable via one of the following methods:
    • Select "Workshop .. Generate the executable". Select "Workshop .. Generate the Windows CE/Mobile application".
    • 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 CE/Mobile application".
  2. The wizard informs you whether some 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 entered in all the languages supported by the current project.
  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. If a library was requested, select the elements (windows, reports, ...) that will be included in the library.
  9. If your project is using external components, specify whether these external components must be included in the executable.
  10. Select (if necessary) the external libraries (".WDL" files) used by the executable program.
  11. Specify the executable information visible in the "Version" tab or in the "Details" tab of the 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. The signature standard used is PKCS7. The WINDEV Mobile libraries are also signed.
      This signature is used to:
      • make sure that the executable was not modified since its generation.
      • use some specific features (sending SMSs for example). See Certificates in Mobile for more details.
      New in version 16
      Signature of the executable: If the executable must be signed, specify the certificate to use. The signature standard used is PKCS7. The WINDEV Mobile libraries are also signed.
      This signature is used to:
      • make sure that the executable was not modified since its generation.
      • use some specific features (sending SMSs for example). See Certificates in Mobile for more details.
      Signature of the executable: If the executable must be signed, specify the certificate to use. The signature standard used is PKCS7. The WINDEV Mobile libraries are also signed.
      This signature is used to:
      • make sure that the executable was not modified since its generation.
      • use some specific features (sending SMSs for example). See Certificates in Mobile for more details.
  12. Specify the information about the executable version.
  13. Specify the mode for using the Framework.
    Notes:
    • If the Mobile executable uses a .NET assembly, the Framework must be installed in the current directory or in the default standard directory.
    • The entire framework can be loaded when starting the application to limit the load errors while using the applications. In this case, check "Load the framework when starting the application". All the DLLs used by the application will be loaded as soon as the application is started (and not when the DLL is used for the first time).
  14. Select (if necessary) the WINDEV Mobile libraries (".DLL" files) used by the executable program.
  15. Specify whether the executable must be copied onto the Pocket PC connected to the current computer.
    • If the executable must not be copied onto the Pocket PC connected to the current computer, the executable creation is completed.
    • If the executable must be copied onto the Pocket PC connected to the current computer, specify the directory where the application (executable, libraries and WINDEV Framework if necessary) must be copied.
      At the end of copy onto the Pocket PC, the executable will be automatically run. Specify a command line if necessary.
      Caution: The directory must be specified according to the notation recognized by the Pocket PC (for example: "\MyApp") and the Pocket PC must be connected to the current computer.
  16. If you have decided to copy the executable to the Pocket PC, select the files to copy. All the files found in the EXE directory of the project will be selected by default. To optimize the time taken to copy the files onto the Pocket PC, you may choose not to copy the large files (marked in red).
  17. Validate the copy and run the executable on the Pocket PC. The wizard is ended.
Note: If a Mobile executable that is using .NET assemblies is run on a Pocket where the .NET 2.0 Framework is not installed, the executable does not operate. No error message is displayed.
Minimum required version
  • Version 9
This page is also available for…
Comments
Click [Add] to post a comment