PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US
  • Overview
  • How to proceed?
  • Creating a configuration
  • Working on a configuration
  • Generating a configuration
  • Adding an element into a configuration
  • Excluding an element from a configuration
  • Duplicating a configuration
  • Deleting a configuration
  • Characteristics of a configuration
  • Tips
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
The project configurations are used to define the different types of generations supported by the project: 32-bit executable, 64-bit executable, webservice, component, ...
The project elements can be:
  • common to several configurations (a window used in a 32-bit executable and in a 64-bit executable for example).
  • specific to a configuration (a class used by a component for example).
You can work on a specific configuration at any time: the elements that do not belong to this configuration will be grayed in the project editor.
This help page presents the following topics:
How to proceed?

Creating a configuration

By default, a single configuration is created in the project. This configuration is named like the project and it contains all project elements.
To create a new configuration:
  1. Select "Project .. Project configurations .. New configuration". You also have the ability to select "New configuration" from the popup menu of "Project explorer" pane.On the "Project" pane, in the "Project configuration" group, click "New configuration" and select "New configuration (via wizard)".
    Notes:
    • You also have the ability to directly select the platform of project configuration to create by expanding "New configuration".
    • You also have the ability to select "New configuration" from the popup menu of "Project explorer" pane.
    Project explorer
  2. The wizard for project configuration starts. Specify:
    • the configuration name.
      Versions 16 and later
      Caution: From version 160056, if the project contains several project configurations, this name will also correspond to the name of directory where the files of project configuration will be generated.
      New in version 16
      Caution: From version 160056, if the project contains several project configurations, this name will also correspond to the name of directory where the files of project configuration will be generated.
      Caution: From version 160056, if the project contains several project configurations, this name will also correspond to the name of directory where the files of project configuration will be generated.
      Caution: If the project contains several project configurations, this name will also correspond to the name of directory where the files of project configuration will be generated.
    • its description.
    • the type of generation: Executable, Java, Library, Component, Webservice, .Net assembly, .Net executable, ...
      This characteristic is not requested if the platform was selected during the creation.
  3. Versions 16 and later
    According to the type of generation chosen for the project configuration, you have the ability to specify the compatibility options of configuration:
    • Multi-product: The element will be generated for a specific type of project or for a use in all products (WINDEV, WEBDEV and WINDEV Mobile).
    • Platform: The compilation errors can be enabled (or not) for the 64-bit or Linux compatibility.
    New in version 16
    According to the type of generation chosen for the project configuration, you have the ability to specify the compatibility options of configuration:
    • Multi-product: The element will be generated for a specific type of project or for a use in all products (WINDEV, WEBDEV and WINDEV Mobile).
    • Platform: The compilation errors can be enabled (or not) for the 64-bit or Linux compatibility.
    According to the type of generation chosen for the project configuration, you have the ability to specify the compatibility options of configuration:
    • Multi-product: The element will be generated for a specific type of project or for a use in all products (WINDEV, WEBDEV and WINDEV Mobile).
    • Platform: The compilation errors can be enabled (or not) for the 64-bit or Linux compatibility.
  4. Specify (if necessary) the project elements that must be included in the project configuration currently created (windows, reports, queries, ...). If your project is using components, you also have the ability to select the components included in the configuration.
  5. Validate the creation of configuration. This project configuration is automatically selected. This configuration can be modified:
    • from the window for project configurations ("Project .. Project configurations .. Manage the configurations"), "Description" button.from the window for project configurations: on the "Project" pane, in the "Project configuration" group, click "Manage the configurations". All you have to do is select the requested configuration and click the "Description" button.
    • via "Description" from the popup menu of project configuration in the "Project explorer" pane.
Project explorer
Versions 16 and later
Directory of project configurations:
From version 160056, when creating a project configuration, the files of this project configuration are generated in a sub-directory of EXE directory of project. This allows you to easily find the files generated by a configuration. When creating a project configuration, the files of this project configuration are generated by default in a sub-directory of EXE directory of project. This allows you to easily find the files generated by a configuration.
If the project already was a multi-configuration project, when creating a project configuration, a wizard plane proposes to generate the configuration files:
  • in the EXE directory of the (operating mode kept for backward compatibility).
  • in a sub-directory for each configuration (created in the EXE directory of project). In this case, a directory is created for each one of the configurations that exists in the project. The name of this directory corresponds to the name of project configuration.
Notes:
  • In the "Options" tab of the description window of project, "Generate all the configurations in the EXE directory" is used to restore the operating mode of earlier versions.
  • In GO mode, the files used are the files found in the configuration directory (INI files, data files, ...).
  • During the first creation of a project configuration, the content of EXE directory is entirely copied into the sub-directories of project configurations. You may have to delete the files not affected by the current configuration (for example, EXE file not required in the directory of a component configuration).
  • Versions 21 and later
    You also have the ability to create a project configuration from an existing configuration. To do so, perform a duplication of configuration.
    New in version 21
    You also have the ability to create a project configuration from an existing configuration. To do so, perform a duplication of configuration.
    You also have the ability to create a project configuration from an existing configuration. To do so, perform a duplication of configuration.
New in version 16
Directory of project configurations:
From version 160056, when creating a project configuration, the files of this project configuration are generated in a sub-directory of EXE directory of project. This allows you to easily find the files generated by a configuration. When creating a project configuration, the files of this project configuration are generated by default in a sub-directory of EXE directory of project. This allows you to easily find the files generated by a configuration.
If the project already was a multi-configuration project, when creating a project configuration, a wizard plane proposes to generate the configuration files:
  • in the EXE directory of the (operating mode kept for backward compatibility).
  • in a sub-directory for each configuration (created in the EXE directory of project). In this case, a directory is created for each one of the configurations that exists in the project. The name of this directory corresponds to the name of project configuration.
Notes:
  • In the "Options" tab of the description window of project, "Generate all the configurations in the EXE directory" is used to restore the operating mode of earlier versions.
  • In GO mode, the files used are the files found in the configuration directory (INI files, data files, ...).
  • During the first creation of a project configuration, the content of EXE directory is entirely copied into the sub-directories of project configurations. You may have to delete the files not affected by the current configuration (for example, EXE file not required in the directory of a component configuration).
  • Versions 21 and later
    You also have the ability to create a project configuration from an existing configuration. To do so, perform a duplication of configuration.
    New in version 21
    You also have the ability to create a project configuration from an existing configuration. To do so, perform a duplication of configuration.
    You also have the ability to create a project configuration from an existing configuration. To do so, perform a duplication of configuration.
Directory of project configurations:
From version 160056, when creating a project configuration, the files of this project configuration are generated in a sub-directory of EXE directory of project. This allows you to easily find the files generated by a configuration. When creating a project configuration, the files of this project configuration are generated by default in a sub-directory of EXE directory of project. This allows you to easily find the files generated by a configuration.
If the project already was a multi-configuration project, when creating a project configuration, a wizard plane proposes to generate the configuration files:
  • in the EXE directory of the (operating mode kept for backward compatibility).
  • in a sub-directory for each configuration (created in the EXE directory of project). In this case, a directory is created for each one of the configurations that exists in the project. The name of this directory corresponds to the name of project configuration.
Notes:
  • In the "Options" tab of the description window of project, "Generate all the configurations in the EXE directory" is used to restore the operating mode of earlier versions.
  • In GO mode, the files used are the files found in the configuration directory (INI files, data files, ...).
  • During the first creation of a project configuration, the content of EXE directory is entirely copied into the sub-directories of project configurations. You may have to delete the files not affected by the current configuration (for example, EXE file not required in the directory of a component configuration).
  • Versions 21 and later
    You also have the ability to create a project configuration from an existing configuration. To do so, perform a duplication of configuration.
    New in version 21
    You also have the ability to create a project configuration from an existing configuration. To do so, perform a duplication of configuration.
    You also have the ability to create a project configuration from an existing configuration. To do so, perform a duplication of configuration.

Working on a configuration

The working configuration is selected:
  • via the "Project explorer" pane: all you have to do is double-click the requested configuration or select "Enable this configuration" from the popup menu.
    Project explorer
  • via the window for project configurations ("Project .. Project configurations .. Manage the configurations"). All you have to do is check the current configuration and validate the window. via the window for project configurations: on the "Project" pane, in the "Project configuration" group, click "Manage the configurations". All you have to do is check the current configuration and validate the window.
The entire project corresponds to the configuration named like the project.
When working on a specific configuration:
  • In the project explorer, the icon found in front of the name of an element not used in the current configuration is grayed.
  • A first window or a first page can be defined for each project configuration.
  • When generating the elements of a configuration, only the elements defined in the configuration are taken into account.
  • In the quick access buttons, the generation icon automatically adapts to the type of configuration used (creation of an executable, creation of a JAVA archive, ...). In the toolbar of the product, the generation icon automatically adapts to the type of configuration used (creation of an executable, creation of a JAVA archive, ...).
    • In the project graph, the project elements nor used in the project configuration are grayed.
    Menu

Generating a configuration

To generate the result of a project configuration:
  1. Display the window for project configurations ("Project .. Project configurations .. Manage the configurations").Display the window for project configurations: on the "Project" pane, in the "Project configuration" group, click "Manage the configurations".
  2. Select the project configuration to generate.
  3. Click the "Generate" button.
To generate the result of all project configurations, use the multiple generation. See Generating project configurations for more details.

Adding an element into a configuration

To add an element into a configuration:
  1. Select the requested project configuration in the "Project explorer" pane.
  2. Select the element to add in the project explorer (window, report, ...).
  3. In the popup menu of element (right mouse click), select "Include in the current configuration".
To add an element into a configuration:
  1. In the "Project explorer" pane, select the element to add (window, report, ...).
  2. Select "Configurations" from the popup menu of element (right mouse click). In the menu that is displayed:
    • the checked configurations correspond to the configurations associated with the element.
    • the unchecked configurations correspond to the configurations not associated with the element.
  3. Select the unchecked configuration into which the element will be added.
Note: When saving a new element, the following window is displayed:
Element backup
This window is used to specify the configuration into which the current element will be added.
In order for this window to be automatically displayed whenever a new element is saved, check "Ask for the location of new elements in the project" in the "Options" tab of project description.

Excluding an element from a configuration

To exclude an element from a configuration:
  1. Select the requested configuration in the "Project explorer" pane.
  2. Select the element to exclude in the "Project explorer" pane (window, report, ...).
  3. Select "Exclude from the current configuration" from the popup menu of element.
To exclude an element from a configuration:
  1. In the "Project explorer" pane, select the element to exclude (window, report, ...).
  2. Select "Configurations" from the popup menu of element (right mouse click). In the menu that is displayed:
    • the checked configurations correspond to the configurations associated with the element.
    • the unchecked configurations correspond to the configurations not associated with the element.
  3. Select the checked configuration for which the element will be excluded.
Versions 21 and later
Note: The elements excluded from a project configuration are not compiled for this project configuration. The element code is grayed.
In the non-compiled code:
  • no assisted code input is available.
  • no cross-reference is available: no Shift+F2, the uses of elements are not displayed, the elements can appear in the list of orphan elements and dead code.
  • there is no code analysis: no smart renaming.
  • there is no compilation error: if the prototype of a procedure is modified, the error will be displayed when using a configuration that allows the code compilation.
New in version 21
Note: The elements excluded from a project configuration are not compiled for this project configuration. The element code is grayed.
In the non-compiled code:
  • no assisted code input is available.
  • no cross-reference is available: no Shift+F2, the uses of elements are not displayed, the elements can appear in the list of orphan elements and dead code.
  • there is no code analysis: no smart renaming.
  • there is no compilation error: if the prototype of a procedure is modified, the error will be displayed when using a configuration that allows the code compilation.
Note: The elements excluded from a project configuration are not compiled for this project configuration. The element code is grayed.
In the non-compiled code:
  • no assisted code input is available.
  • no cross-reference is available: no Shift+F2, the uses of elements are not displayed, the elements can appear in the list of orphan elements and dead code.
  • there is no code analysis: no smart renaming.
  • there is no compilation error: if the prototype of a procedure is modified, the error will be displayed when using a configuration that allows the code compilation.
Versions 21 and later

Duplicating a configuration

To duplicate a configuration:
  1. Display the window for project configurations: on the "Project" pane, in the "Project configuration" group, click "Manage the configurations".
  2. Select the project configuration to duplicate.
  3. Click the "Duplicate" button.
  4. Modify (if necessary) the new project configuration:
    • Click the "Description" button.
    • In the "General" tab, modify the duplicated configuration: the name, the type of generation and the generation directory of configuration.
Notes:
  • The duplicated configuration and the source configuration contain the same elements. This allows you to easily create an iOS configuration in an Android project.
  • The name of generated element must be modified if necessary in the corresponding generation wizard.
New in version 21

Duplicating a configuration

To duplicate a configuration:
  1. Display the window for project configurations: on the "Project" pane, in the "Project configuration" group, click "Manage the configurations".
  2. Select the project configuration to duplicate.
  3. Click the "Duplicate" button.
  4. Modify (if necessary) the new project configuration:
    • Click the "Description" button.
    • In the "General" tab, modify the duplicated configuration: the name, the type of generation and the generation directory of configuration.
Notes:
  • The duplicated configuration and the source configuration contain the same elements. This allows you to easily create an iOS configuration in an Android project.
  • The name of generated element must be modified if necessary in the corresponding generation wizard.

Duplicating a configuration

To duplicate a configuration:
  1. Display the window for project configurations: on the "Project" pane, in the "Project configuration" group, click "Manage the configurations".
  2. Select the project configuration to duplicate.
  3. Click the "Duplicate" button.
  4. Modify (if necessary) the new project configuration:
    • Click the "Description" button.
    • In the "General" tab, modify the duplicated configuration: the name, the type of generation and the generation directory of configuration.
Notes:
  • The duplicated configuration and the source configuration contain the same elements. This allows you to easily create an iOS configuration in an Android project.
  • The name of generated element must be modified if necessary in the corresponding generation wizard.

Deleting a configuration

To delete a configuration:
  1. Select the requested configuration in the "Project explorer" pane.
  2. Select "Delete" from the menu of the "Project explorer" pane.
Notes:
  • The configuration elements will be stored in the project (windows, reports, ...).
  • The generated elements (executable, service, component, ...) will not be deleted from disk.

Characteristics of a configuration

To modify a project configuration, select "Project .. Project configurations .. Manage the configurations". To modify a project configuration, on the "Project" pane, in the "Project configuration" group, click "Manage the configurations".
The window for managing the configurations allows you to describe:
  • a command line for running the test of project configuration: "Test mode" button.
  • the action to perform before generating the project configuration: "Action before generation" button. All you have to do is specify the action to perform at the time of generation.
  • the action to perform after generating the project configuration: "Action after generation" button. All you have to do is specify the action to perform after the generation.
The "Description" button opens the window for describing the configuration. This window contains the following elements:
  • the main element of project configuration ("General" tab).
  • the animations for opening and/or closing the windows found in the project configuration: "Animations of windows" button ("Elements" tab).
  • all components used by the project configuration ("Components" tab).
  • all elements found in the project configuration ("Elements" tab).
  • the general information: the configuration name and description ("General" tab).
  • the generation information:
    • Versions 21 and later
      the type of generation ("General" tab).
      New in version 21
      the type of generation ("General" tab).
      the type of generation ("General" tab).
    • Versions 16 and later
      the directory for generating the project configuration if the project contains several configurations ("General" tab).
      New in version 16
      the directory for generating the project configuration if the project contains several configurations ("General" tab).
      the directory for generating the project configuration if the project contains several configurations ("General" tab).
    • the actions to perform before and after generating the project configuration ("General" tab).
    • Versions 23 and later
      Versions ANDROID and later
      the actions to perform before the Gradle generation ("General" tab).
      New in version ANDROID
      the actions to perform before the Gradle generation ("General" tab).
      the actions to perform before the Gradle generation ("General" tab).
      New in version 23
      Versions ANDROID and later
      the actions to perform before the Gradle generation ("General" tab).
      New in version ANDROID
      the actions to perform before the Gradle generation ("General" tab).
      the actions to perform before the Gradle generation ("General" tab).
      Versions ANDROID and later
      the actions to perform before the Gradle generation ("General" tab).
      New in version ANDROID
      the actions to perform before the Gradle generation ("General" tab).
      the actions to perform before the Gradle generation ("General" tab).
  • the first windows or first pages.
    • WINDEVWINDEV Mobile the first project window: Allows you to select the first window that will be displayed when starting the project (or the associated executable).
      The [...] button is used to preview all project windows for fast selection.
      See First project window for more details.
    • WEBDEV - Server code the home page: Used to select the site home page.
      The [...] button is used to preview all project pages for fast selection.
      See The home page for more details.
    • WEBDEV - Server code the first dynamic page: Used to select the first dynamic page of project.
      The [...] button is used to preview all dynamic project pages for fast selection.
      See First dynamic project page for more details.
    • WEBDEV - Server code the error page: Allows you to select the page used to display the site errors.
      The [...] button is used to preview all static project pages for fast selection.
      See A specific page to display the errors for more details.
  • Versions 21 and later
    the executable characteristics.
    • The "Cryptable executable" option is used to make the generated executables compatible with the tools for encrypting and compressing executables (UPX, HASP envelope, ...).
    • Versions 23 and later
      The option "Disable the prevention from running data (/NXCOMPAT:NO option)" is used to manage the "NX" compilation option (No eXecute).
      • The 32-bit executables and DLLs for Windows are now compiled with the "NX" option (No eXecute). This option is commended to improve security. It must necessarily be used in order for an application to be certified by Microsoft for example. Indeed, an application compiled without this option can allow his author ro run a code that was placed at a specific memory location. This technique, already used by malevolent applications, is not allowed anymore.
      • The option "Disable the prevention from running data (/NXCOMPAT:NO option)" is used to compile without the "NX" option. This may be required when the executable is using an external DLL (ActiveX, ODBC driver for accessing a database, ...), that has no NX flag and that runs code in memory via what could be a security breach. If the main application is compiled with the NX option, it will be stopped by Windows in general protection fault (GPF).
      • Notes:
        • We advise you to solicit the DLL publisher in order to get a refreshed version of DLL with the NX flag.
        • We advise you to foresee in the medium term an alternative to the use of DLL. Indeed, with the increased security of systems, it is quite possible that the executables without the NX option may no longer be run in the near future.
      New in version 23
      The option "Disable the prevention from running data (/NXCOMPAT:NO option)" is used to manage the "NX" compilation option (No eXecute).
      • The 32-bit executables and DLLs for Windows are now compiled with the "NX" option (No eXecute). This option is commended to improve security. It must necessarily be used in order for an application to be certified by Microsoft for example. Indeed, an application compiled without this option can allow his author ro run a code that was placed at a specific memory location. This technique, already used by malevolent applications, is not allowed anymore.
      • The option "Disable the prevention from running data (/NXCOMPAT:NO option)" is used to compile without the "NX" option. This may be required when the executable is using an external DLL (ActiveX, ODBC driver for accessing a database, ...), that has no NX flag and that runs code in memory via what could be a security breach. If the main application is compiled with the NX option, it will be stopped by Windows in general protection fault (GPF).
      • Notes:
        • We advise you to solicit the DLL publisher in order to get a refreshed version of DLL with the NX flag.
        • We advise you to foresee in the medium term an alternative to the use of DLL. Indeed, with the increased security of systems, it is quite possible that the executables without the NX option may no longer be run in the near future.
      The option "Disable the prevention from running data (/NXCOMPAT:NO option)" is used to manage the "NX" compilation option (No eXecute).
      • The 32-bit executables and DLLs for Windows are now compiled with the "NX" option (No eXecute). This option is commended to improve security. It must necessarily be used in order for an application to be certified by Microsoft for example. Indeed, an application compiled without this option can allow his author ro run a code that was placed at a specific memory location. This technique, already used by malevolent applications, is not allowed anymore.
      • The option "Disable the prevention from running data (/NXCOMPAT:NO option)" is used to compile without the "NX" option. This may be required when the executable is using an external DLL (ActiveX, ODBC driver for accessing a database, ...), that has no NX flag and that runs code in memory via what could be a security breach. If the main application is compiled with the NX option, it will be stopped by Windows in general protection fault (GPF).
      • Notes:
        • We advise you to solicit the DLL publisher in order to get a refreshed version of DLL with the NX flag.
        • We advise you to foresee in the medium term an alternative to the use of DLL. Indeed, with the increased security of systems, it is quite possible that the executables without the NX option may no longer be run in the near future.
    New in version 21
    the executable characteristics.
    • The "Cryptable executable" option is used to make the generated executables compatible with the tools for encrypting and compressing executables (UPX, HASP envelope, ...).
    • Versions 23 and later
      The option "Disable the prevention from running data (/NXCOMPAT:NO option)" is used to manage the "NX" compilation option (No eXecute).
      • The 32-bit executables and DLLs for Windows are now compiled with the "NX" option (No eXecute). This option is commended to improve security. It must necessarily be used in order for an application to be certified by Microsoft for example. Indeed, an application compiled without this option can allow his author ro run a code that was placed at a specific memory location. This technique, already used by malevolent applications, is not allowed anymore.
      • The option "Disable the prevention from running data (/NXCOMPAT:NO option)" is used to compile without the "NX" option. This may be required when the executable is using an external DLL (ActiveX, ODBC driver for accessing a database, ...), that has no NX flag and that runs code in memory via what could be a security breach. If the main application is compiled with the NX option, it will be stopped by Windows in general protection fault (GPF).
      • Notes:
        • We advise you to solicit the DLL publisher in order to get a refreshed version of DLL with the NX flag.
        • We advise you to foresee in the medium term an alternative to the use of DLL. Indeed, with the increased security of systems, it is quite possible that the executables without the NX option may no longer be run in the near future.
      New in version 23
      The option "Disable the prevention from running data (/NXCOMPAT:NO option)" is used to manage the "NX" compilation option (No eXecute).
      • The 32-bit executables and DLLs for Windows are now compiled with the "NX" option (No eXecute). This option is commended to improve security. It must necessarily be used in order for an application to be certified by Microsoft for example. Indeed, an application compiled without this option can allow his author ro run a code that was placed at a specific memory location. This technique, already used by malevolent applications, is not allowed anymore.
      • The option "Disable the prevention from running data (/NXCOMPAT:NO option)" is used to compile without the "NX" option. This may be required when the executable is using an external DLL (ActiveX, ODBC driver for accessing a database, ...), that has no NX flag and that runs code in memory via what could be a security breach. If the main application is compiled with the NX option, it will be stopped by Windows in general protection fault (GPF).
      • Notes:
        • We advise you to solicit the DLL publisher in order to get a refreshed version of DLL with the NX flag.
        • We advise you to foresee in the medium term an alternative to the use of DLL. Indeed, with the increased security of systems, it is quite possible that the executables without the NX option may no longer be run in the near future.
      The option "Disable the prevention from running data (/NXCOMPAT:NO option)" is used to manage the "NX" compilation option (No eXecute).
      • The 32-bit executables and DLLs for Windows are now compiled with the "NX" option (No eXecute). This option is commended to improve security. It must necessarily be used in order for an application to be certified by Microsoft for example. Indeed, an application compiled without this option can allow his author ro run a code that was placed at a specific memory location. This technique, already used by malevolent applications, is not allowed anymore.
      • The option "Disable the prevention from running data (/NXCOMPAT:NO option)" is used to compile without the "NX" option. This may be required when the executable is using an external DLL (ActiveX, ODBC driver for accessing a database, ...), that has no NX flag and that runs code in memory via what could be a security breach. If the main application is compiled with the NX option, it will be stopped by Windows in general protection fault (GPF).
      • Notes:
        • We advise you to solicit the DLL publisher in order to get a refreshed version of DLL with the NX flag.
        • We advise you to foresee in the medium term an alternative to the use of DLL. Indeed, with the increased security of systems, it is quite possible that the executables without the NX option may no longer be run in the near future.
    the executable characteristics.
    • The "Cryptable executable" option is used to make the generated executables compatible with the tools for encrypting and compressing executables (UPX, HASP envelope, ...).
    • Versions 23 and later
      The option "Disable the prevention from running data (/NXCOMPAT:NO option)" is used to manage the "NX" compilation option (No eXecute).
      • The 32-bit executables and DLLs for Windows are now compiled with the "NX" option (No eXecute). This option is commended to improve security. It must necessarily be used in order for an application to be certified by Microsoft for example. Indeed, an application compiled without this option can allow his author ro run a code that was placed at a specific memory location. This technique, already used by malevolent applications, is not allowed anymore.
      • The option "Disable the prevention from running data (/NXCOMPAT:NO option)" is used to compile without the "NX" option. This may be required when the executable is using an external DLL (ActiveX, ODBC driver for accessing a database, ...), that has no NX flag and that runs code in memory via what could be a security breach. If the main application is compiled with the NX option, it will be stopped by Windows in general protection fault (GPF).
      • Notes:
        • We advise you to solicit the DLL publisher in order to get a refreshed version of DLL with the NX flag.
        • We advise you to foresee in the medium term an alternative to the use of DLL. Indeed, with the increased security of systems, it is quite possible that the executables without the NX option may no longer be run in the near future.
      New in version 23
      The option "Disable the prevention from running data (/NXCOMPAT:NO option)" is used to manage the "NX" compilation option (No eXecute).
      • The 32-bit executables and DLLs for Windows are now compiled with the "NX" option (No eXecute). This option is commended to improve security. It must necessarily be used in order for an application to be certified by Microsoft for example. Indeed, an application compiled without this option can allow his author ro run a code that was placed at a specific memory location. This technique, already used by malevolent applications, is not allowed anymore.
      • The option "Disable the prevention from running data (/NXCOMPAT:NO option)" is used to compile without the "NX" option. This may be required when the executable is using an external DLL (ActiveX, ODBC driver for accessing a database, ...), that has no NX flag and that runs code in memory via what could be a security breach. If the main application is compiled with the NX option, it will be stopped by Windows in general protection fault (GPF).
      • Notes:
        • We advise you to solicit the DLL publisher in order to get a refreshed version of DLL with the NX flag.
        • We advise you to foresee in the medium term an alternative to the use of DLL. Indeed, with the increased security of systems, it is quite possible that the executables without the NX option may no longer be run in the near future.
      The option "Disable the prevention from running data (/NXCOMPAT:NO option)" is used to manage the "NX" compilation option (No eXecute).
      • The 32-bit executables and DLLs for Windows are now compiled with the "NX" option (No eXecute). This option is commended to improve security. It must necessarily be used in order for an application to be certified by Microsoft for example. Indeed, an application compiled without this option can allow his author ro run a code that was placed at a specific memory location. This technique, already used by malevolent applications, is not allowed anymore.
      • The option "Disable the prevention from running data (/NXCOMPAT:NO option)" is used to compile without the "NX" option. This may be required when the executable is using an external DLL (ActiveX, ODBC driver for accessing a database, ...), that has no NX flag and that runs code in memory via what could be a security breach. If the main application is compiled with the NX option, it will be stopped by Windows in general protection fault (GPF).
      • Notes:
        • We advise you to solicit the DLL publisher in order to get a refreshed version of DLL with the NX flag.
        • We advise you to foresee in the medium term an alternative to the use of DLL. Indeed, with the increased security of systems, it is quite possible that the executables without the NX option may no longer be run in the near future.
  • Versions 21 and later
    Android the appearance options:
    • the use of "Material Design" theme ("General" tab, "Apply the Material Design theme to the native controls and to the Info/Error/Dialog windows (requires Android 5.0 or later)" option). If this option is not checked, the holographic theme is used by default.
    • Versions 23 and later
      the positioning of captions compatible with version 22: From version 23, the display of window editor becomes even more WYSIWYG: the padding specified in the fonts is now taken into account. The option "positioning of captions compatible with version 22" is used to restore the display of version 22 (for the projects created in an earlier version for example).
      New in version 23
      the positioning of captions compatible with version 22: From version 23, the display of window editor becomes even more WYSIWYG: the padding specified in the fonts is now taken into account. The option "positioning of captions compatible with version 22" is used to restore the display of version 22 (for the projects created in an earlier version for example).
      the positioning of captions compatible with version 22: From version 23, the display of window editor becomes even more WYSIWYG: the padding specified in the fonts is now taken into account. The option "positioning of captions compatible with version 22" is used to restore the display of version 22 (for the projects created in an earlier version for example).
    New in version 21
    Android the appearance options:
    • the use of "Material Design" theme ("General" tab, "Apply the Material Design theme to the native controls and to the Info/Error/Dialog windows (requires Android 5.0 or later)" option). If this option is not checked, the holographic theme is used by default.
    • Versions 23 and later
      the positioning of captions compatible with version 22: From version 23, the display of window editor becomes even more WYSIWYG: the padding specified in the fonts is now taken into account. The option "positioning of captions compatible with version 22" is used to restore the display of version 22 (for the projects created in an earlier version for example).
      New in version 23
      the positioning of captions compatible with version 22: From version 23, the display of window editor becomes even more WYSIWYG: the padding specified in the fonts is now taken into account. The option "positioning of captions compatible with version 22" is used to restore the display of version 22 (for the projects created in an earlier version for example).
      the positioning of captions compatible with version 22: From version 23, the display of window editor becomes even more WYSIWYG: the padding specified in the fonts is now taken into account. The option "positioning of captions compatible with version 22" is used to restore the display of version 22 (for the projects created in an earlier version for example).
    Android the appearance options:
    • the use of "Material Design" theme ("General" tab, "Apply the Material Design theme to the native controls and to the Info/Error/Dialog windows (requires Android 5.0 or later)" option). If this option is not checked, the holographic theme is used by default.
    • Versions 23 and later
      the positioning of captions compatible with version 22: From version 23, the display of window editor becomes even more WYSIWYG: the padding specified in the fonts is now taken into account. The option "positioning of captions compatible with version 22" is used to restore the display of version 22 (for the projects created in an earlier version for example).
      New in version 23
      the positioning of captions compatible with version 22: From version 23, the display of window editor becomes even more WYSIWYG: the padding specified in the fonts is now taken into account. The option "positioning of captions compatible with version 22" is used to restore the display of version 22 (for the projects created in an earlier version for example).
      the positioning of captions compatible with version 22: From version 23, the display of window editor becomes even more WYSIWYG: the padding specified in the fonts is now taken into account. The option "positioning of captions compatible with version 22" is used to restore the display of version 22 (for the projects created in an earlier version for example).
  • all elements found in the project configuration ("Elements" tab).
  • the animations for opening and/or closing the windows found in the project configuration: "Animations of windows" button ("Elements" tab). See Window animation for more details.
  • all components used by the project configuration ("Components" tab).
  • Versions 16 and later
    the compatibility options of project configuration ("Compatibility" tab). The available options are as follows:
    • Multi-product: The element will be generated for a specific type of project or for a use in all products (WINDEV, WEBDEV and WINDEV Mobile).
    • Platform: The compilation errors can be enabled (or not) for the 64-bit or Linux compatibility.
    New in version 16
    the compatibility options of project configuration ("Compatibility" tab). The available options are as follows:
    • Multi-product: The element will be generated for a specific type of project or for a use in all products (WINDEV, WEBDEV and WINDEV Mobile).
    • Platform: The compilation errors can be enabled (or not) for the 64-bit or Linux compatibility.
    the compatibility options of project configuration ("Compatibility" tab). The available options are as follows:
    • Multi-product: The element will be generated for a specific type of project or for a use in all products (WINDEV, WEBDEV and WINDEV Mobile).
    • Platform: The compilation errors can be enabled (or not) for the 64-bit or Linux compatibility.
  • Versions 17 and later
    the use of ANSI or UNICODE strings at run time ("Unicode" tab).
    New in version 17
    the use of ANSI or UNICODE strings at run time ("Unicode" tab).
    the use of ANSI or UNICODE strings at run time ("Unicode" tab).
  • Versions 21 and later
    WINDEV the telemetry options ("Telemetry" tab). The "Telemetry" tab is used to enable the telemetry for the current configuration by specifying its parameters. See Enabling the telemetry for more details.
    New in version 21
    WINDEV the telemetry options ("Telemetry" tab). The "Telemetry" tab is used to enable the telemetry for the current configuration by specifying its parameters. See Enabling the telemetry for more details.
    WINDEV the telemetry options ("Telemetry" tab). The "Telemetry" tab is used to enable the telemetry for the current configuration by specifying its parameters. See Enabling the telemetry for more details.
    WINDEVWINDEV Mobile the telemetry options ("Telemetry" tab). The "Telemetry" tab is used to enable the telemetry for the current configuration by specifying its parameters. See Enabling the telemetry for more details.
For the actions before and after generation, the following operations must be performed:
  1. Type the command script to run. You can type:
    • the executable path: type the path in the control or use the "Browse..." button.
    • macros: click the "Macro" button and double-click the macro that will be added to your command line. For example, "Name of Current Project" {$ProjectName} will be replaced by the name of your project currently edited. A specific macro is used to run an option of a CustomMenu.
  2. Select the runtime options of command line:
    • Display the console: a console (command prompt) will be displayed.
    • Leave the console opened: if a console is displayed, it will remain opened until the end of execution of program run.
    • Non-locking execution: the execution of the command line will not lock the access to WINDEV, WEBDEV or WINDEV Mobile.
  3. Select the runtime directory of program.
  4. Validate

Tips

  • To find out the project configuration by programming, use ProjectInfo associated with the piConfiguration constant.
  • To enable a project configuration from the project explorer, all you have to do is double-click the name of requested configuration. To display the description window of selected configuration, select "Description" from the popup menu.
  • Versions 16 and later
    To directly open the generation directory of a configuration, select "Open the generation directory" from the popup menu of project configuration.
    New in version 16
    To directly open the generation directory of a configuration, select "Open the generation directory" from the popup menu of project configuration.
    To directly open the generation directory of a configuration, select "Open the generation directory" from the popup menu of project configuration.
Minimum required version
  • Version 9
This page is also available for…
Comments
Click [Add] to post a comment