|
|
|
|
|
|
|
|
|
|
- Overview
- Disabling JITc
- Managing the automatic user tests
- Enabling the dynamic audit
- Enable runtime log
- Connections used by the application
- Disabling the telemetry on an application
The <Executable Name>.WX file is used to manage some features directly, even if these features have not been included in the application. This file is found beside the executable. This file is a text file containing different sections that correspond to the requested features. You can manage: The principle behind JITc (Just In Time Compilation) technology is very simple: WINDEV's L5G code is transformed on the runtime machine into "native assembly code" as it is executed.. For more details, see JITc. If you have suspicions about problems that may be caused by the JIT technology, this technology can be disabled for a specific application, by modifying (or by adding) the <Executable Name>.WX file. This file is found beside the executable. To disable the JITc technology, add the following lines: [WD_EXECUTION]
OPTIM_EXECUTION=0 Managing the automatic user tests WINDEV allows the user to record a test scenario in order to send it to the quality service or to the developer. Therefore, the user can easily transmit a reproduction protocol that is difficult to explain. The developer will be able to import the tests directly into his project. These tests can be run to reproduce the problem encountered by the user and they can be added to the automated tests of the application. The creation of a test scenario can be done without modifying the application, via the <Executable Name>.WX file. This file must contain the following lines: [Scenario] Enabled = <0/1> File = <Name of WSCT file> DLLPath = <DLL path for test> Let's take a look at these lines: - Active: This parameter must correspond to 0 for not recording, and 1 for recording the scenario.
- File: Scenario file name (file extension "wsct"). This name can be built from the following elements:
| | | [%ExeDir%] | Directory of the executable, always filled with the "\" character. This directory is equivalent to the result of fExeDir. | | [%ExeName%] | Executable name. | | [%Date%] | Start date of scenario file. | | [%Time%] | Start time of scenario file. | | [%UserName%] | Name of the current user. | | [%ComputerName%] | Computer name. | | [%DataDir%] | Directory of the HFSQL data files specified by the user when installing the application. This directory is equivalent to the result of fDataDir. | | [%DirUserData%] | Directory for the data of the current user of the current application. This directory is equivalent to the result of fDataDirUser. |
- PathDLL: path to wd300test.dll library. This DLL is required to create the scenario.
Enabling the dynamic audit The dynamic audit of an application analyzes its runtime performance. A dynamic audit can be performed in a test environment or on a live application. The audit detects problems such as: - Excessive memory consumption
- Slowness of algorithms used
- Errors "hidden" at runtime
It is possible to audit an application in its production environment without modifying the executable: simply create a file in the same directory as the executable, with the same name and ".WX" extension. This file will have the following format: [AUDIT] ENABLED = 1 (or 0 to disable the audit) FILE = <path of the .waudit file to be generated> OPTION = <combination of the options of dbgEnableAudit> The runtime log is a runtime trace. This log is a simple file (wlog extension) that contains the details of all the operations performed by a user in a WINDEV application: - details about the processes called,
- WLanguage functions with their parameters,
- user procedures with their parameters,
- threads,
- components.
This file is used to: - identify the most frequent actions in the application.
- determine which processes take the longest.
- follow the code run during a process that triggers problems (hard to isolate in test mode).
The activation of runtime log can be done without modifying the application via a specific file. To do so, create a file named <Executable Name>.WX beside the executable of the application. This file must contain the following lines: [LOG]
Enabled=<0/1>
File=<Name of the WXL file>
Option=<Value of options> Let's take a closer look at these lines: - Active: This parameter must be 0 to disable the log and 1 to enable it.
- File: Name of log file (file with "wxl" extension). This name can be built from the following elements:
| | | [%ExeDir%] | Directory of the executable, always filled with the "\" character. This directory is equivalent to the result of fExeDir. | | [%ExeName%] | Executable name. | | [%Date%] | Start date of Log file. | | [%Time%] | Start time of Log file. | | [%UserName%] | Name of the current user. | | [%ComputerName%] | Computer name. | | [%DataDir%] | Directory of the HFSQL data files specified by the user when installing the application. This directory is equivalent to the result of fDataDir. | | [%DirUserData%] | Directory for the data of the current user of the current application. This directory is equivalent to the result of fDataDirUser. |
- Option: Log file options.
- If options are not specified in the WX file (the OPTION line is not present), the log file is created with default options: only WLanguage functions are present in the log file.
- "" (empty string): Only processes are stored in the log.
- "*": the log contains all the information.
- a combination of values:
- "+F" to enable the trace for the functions,
- "+P" to enable the trace for the parameters.
Connections used by the application When the application is installed on the end-user computer, depending on the selected options, the wizard allows the user to install an HFSQL Client/Server server on a Windows or Linux computer and to configure the connection used. At the end of setup, a ".wx" file is created beside the executable. The structure of this file is given for information. This structure can be modified in a forthcoming version. This file should not be modified manually. This file contains the following information: [CONNECT]
NBCX = Number of defined connections
NOM_x = Name of the connection number x
BASE_x = Type of database used (always corresponds to hAccessHFClientServer)
ADRESSE_x = Address of server used (name or IP address of the server)
PORT_x = Connection port
DATABASE_x = Name of the database used
LOGIN_x = Connection login
PWD_x = Encrypted password
ACCESS_x = Type of access (hOReadWrite or hORead)
EXTINFO_x = Extended information Disabling the telemetry on an application The telemetry allows you to collect information about the use of an application by the end users. For more details, see Telemetry: Overview. You have the ability to disable the telemetry in an application: - by calling the TelemetryDisable function.
- by re-installing the application and by unchecking "Participate to the improvement...".
- via the <Executable Name>.WX file. This file must contain the following lines:
Note: This entry is not present at all in the <Nom exécutable>.WX file if telemetry is active.
This page is also available for…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|