Extract
[...] When modifications to the system require administrator-level authorization, the User Account Control notifies the user, giving them the option to approve or deny the modification. You may want to modify the settings of these 2 screens UAC improves the security of Windows devices by limiting the access that malicious code has to run with administrator privileges. UAC enables users to make informed decisions about actions that could affect the stability and security of their device. [...]
[...] These are entirely optional information, but that we can place here Then, we have THE EXECUTABLE VERSION This will be VERSION 1 This version will be automatically incremented every time we will manage the executable We can also enter the version number that suits us (we are not obliged to follow what WINDEV proposes) Click on NEXT The User Account Control (UAC) in WinDev is an essential feature that allows for effective management of users and access rights. Here's how it works : The User Account Control (UAC) is a Windows security feature designed to protect the operating system from unauthorized modifications. [...]
[...] WINDEV can create multilingual applications Here we only have French, of which we remain on French Click on NEXT These are the different elements that we have created throughout the training, and WINDEV asks us which ones we want to integrate into our executable, and especially into the LIBRARY It is better to trust WINDEV and all the present elements are necessary for the functioning of the application So we leave them all, of course In general, we do not remove elements, we rather add them in the case of a more elaborate and more complex development, and we may have elements that WINDEV does not know that they must be integrated, but which are necessary for the application, and we will therefore add them here Here we just click on next" What will be the directory in which the data files will be stored. There are several solutions, several systems of operation The data files can be stored for example at the same level as the executable (in some cases, this can be an interesting option) Or else in a specific directory, whose precise path is given Or you let WINDEV handle this automatically: In this case, the data will be placed generally in the user profile directories, so everything that is APP DATA, etc. [...]
[...] User Account Control is enabled by default and can be configured if you have administrative privileges. We don't touch anything and click on NEXT The screen displays that it's finished We click on the FINISH button And the executable will be generated The executable has been generated and everything went well WINDEV proposes to me: - Le lancer - To open the generation directory - To finish It may be interesting to go see what he has created in the generation directory Click on this BUTTON The directory will open in the WINDOWS EXPLORER We are in the generation directory of the application, that is to say the EXE folder in the project DLL files And data files All that's left is to test it by clicking on the executable Everything works correctly, and the data is also there As you have seen, it is very simple to create an executable from a WINDEV project It's enough to follow the different steps proposed by the ASSISTANT In practice, one can be content to generate the executable in this way and install it manually either: - On the workstations - Either on a shared directory for example on the network and put a shortcut then on the workstations of the users - Or else do something more elaborate, generate an installation program, like what is usually found in all professional applications. [...]
[...] WINDEV 28 Express - Generate the Windows executable SUMMARY CREATION OF THE EXECUTABLE EXECUTABLE NAME CREATION OF THE ICON THAT REPRESENTS THE EXECUTABLE PARAMETERIZATION OF THE GENERATED ICON OPERATION OF THE EXECUTABLE PERSONALIZED ERROR MESSAGE TELEMETRY PATCH LIBRARY EXECUTABLE LANGUAGE ADDED TO LIBRARY FILE DIRECTORY HFSQL EXECUTABLE INFORMATION EXECUTABLE VERSION NUMBER USER ACCOUNT CONTROL RUN THE EXECUTABLE Now that our application is functional, we will be able to create the EXECUTABLE That is the EXE program that will be launched from WINDOWS And we will see the installation procedure next To begin with, we will see how to ask WINDEV to trigger the creation of the EXECUTABLE - What are the different OPTIONS and questions that are asked of you as you generate this executable - How to TESTER We will take up our WINDEV project again, and follow the explanations CREATION OF THE EXECUTABLE - DIFFERENT OPTIONS - TEST OF THE GENERATED EXE My WINDEV project is open All windows are closed We will consider that the Application is finished We will position ourselves on CREATE EXECUTABLE Below the executable, we have 2 options: - Executable WINDOWS 32 bits - Create the installation procedure For now we will just generate the EXECUTABLE Click on NEXT WINDEV first asks for the EXECUTABLE NAME We will type: MY PROJECT.EXE Then we can select an ICON that will represent the EXECUTABLE Like all WINDOWS executables, your program can have an ICON We click on the RIGHT BUTTON And select CATALOGUE for example, to choose an icon among the different icons proposed by WINDEV I take for example that one, and I click on OK I have this dialog box We do not make any modifications and click on OK We go back to CREATION OF THE EXECUTABLE We click on NEXT When we are going to GENERATE THE EXECUTABLE, WINDEV will generate a file that we call the LIBRARY and which has the extension WDL like WINDEV LIBRARY, which corresponds to the different elements that we have created (windows, states, requests?) These elements will be contained in the file: this file can be contained in the executable, or as a separate file. In general, there is no need to separate it, so I integrate it into the executable Will my application be MULTI-INSTANCE ??? That is to say: can I launch it several times at the same time? [...]
