• Creating the executable.
• Help about the new features.
• Creating the setup.

	Estimated time: 30 mn

• Open the project you worked on in the previous lesson.
  1. Go to the WINDEV home page (Ctrl + <).
  2. On the home page, click "Tutorial", then in "Part 4 - Full application with data", double-click "Full application - Exercise".
  3. A dialogue box prompts you to open the project you worked on in the previous lesson. You can open the local copy or the original project. Select "Open the local copy".

	Answers	A completed project is available. You can use this project to complete the different exercises of this lesson. To open the completed project, go to the home page and click "Tutorial", then in "Part 4 - Full application with data", double-click "Full application - Answers".

• To create the executable:
  1. Expand in the quick access area, and select "Generate 64-bit Windows executable (.exe)".
     
     
     

     	Note	WINDEV also allows you to create 64-bit executables, Linux executables, services, Java applications and more.
  2. The executable creation wizard starts.
  3. Describe the general options of the executable:
     • the executable name: we will keep the default name.
     • the name of icon associated with the executable: you have the ability to select an icon in the image catalog.
     • the splash screen. Several types of splash screens are available.
       

       	Express	This option is not available in the Express version.

       
     Keep "No splash screen" and go to the next step.
  4. Keep the default options for the operating mode of the executable. Go to the next step.
  5. You can customize the application error message. We will keep the default message. Go to the next step.
  6. The wizard proposes to enable the telemetry in the application. We won't use this feature. Go to the next step.
     

     	Note	Telemetry allows you to get detailed statistics about the use of your application by the end users. It shows you a report of the deployed applications, so you can improve them. For more information on how to set up and configure the telemetry, see Telemetry overview.
  7. This step is used to specify whether the executable will take the patches into account.
     

     	Note	To avoid providing the entire executable again when you make changes to the application, you can distribute the additional resources (windows, reports, etc.) as patches. Patches are additional libraries. If the "Yes: the executable will take these updates by patch into account" option was checked when the executable was created, the elements in the patch will replace the elements in the application library when the application starts. For more details, see Application patch.

     Keep the default options. Go to the next step.
  8. This step allows you to define the executable languages. The multilingual feature will be presented in another lesson. Keep the default options. Go to the next step.
  9. This step displays all files that will be included in the executable library. Those are the project elements that can be handled by the end user. Keep the default options. Go to the next step.
  10. This step concerns the directory of HFSQL Classic data files used by the application.
      
      Select "Automatic (recommended)" if necessary. This option is used to install the data files:
      • in the application data directory (if the executable is installed in "Program files").
      • in the executable directory.
  11. Go to the next step.
  12. We will enter the executable information. This information is displayed in Windows explorer when you select the file properties.
      Enter the following information:
      
      This step can also be used to sign the executable if necessary.
      Go to the next step.
  13. This step allows you to define the executable version number. You can use:
      • a format compatible with the earlier WINDEV versions,
      • a standard Windows format. Select this option.
  14. Go to the next step of the wizard.
  15. We are now going to define the options for integrating the WINDEV framework.
      

      	Express	This option is not available in the Express version.

      
      

      	Note	The framework corresponds to the different libraries required to run the executable.

      The option "Framework DLL in the same location as the executable" allows you to use the necessary libraries only. These DLLs are copied to the executable directory.
      The "Framework embedded in the executable" option allows you to distribute only the executable (since the DLLs are in the executable).
      The option "Common framework" allows you to use the framework common to all the WINDEV applications installed on the computer. With this option, the framework is installed once only on the computer (it can also be downloaded by Internet) and is used by all WINDEV applications.
  16. Select "Common framework" and choose "Common WINDEV framework".
      Go to the next step.
  17. This step applies to Windows Vista (and later). You can include a manifest for Windows Vista (and later).
      For our example, check "Don't include a manifest for Windows Vista and later".
      Go to the next step.
  18. WINDEV proposes to make a backup copy of the project. This backup is used to keep a project version whenever the executable is created. In this case, select "No: Don't make a backup copy of the project" and validate the wizard.
  19. The executable is created. It can be run immediately to check its operating mode. To do so, click "Run executable".

	Note	You can also select a specific step in the wizard to access it directly. The default options of the other steps will be automatically validated.

• To create the setup program:
  1. On the "Project" tab, in the "Generation" group, expand "Setup procedure" and select "Create setup procedure". The executable and setup creation wizard starts.
  2. The executable has already been created: the selected options were saved.
  3. In the wizard, click "Additional information" in the "Executable" section.
  4. The wizard proposes to make a backup copy of the project. Select "No: Don't make a backup copy of the project" and go to the next step.
  5. The wizard proposes to create the new features page.
     

     	Express	This option is not available in the Express version. In this case, go to step 8 directly.

     
     This option is used to create a help file in order to present the new features to the end users. During the first setup, it can be the software help.
     Select "Create a documentation for the new features" and go to the next step.
  6. You have the ability to define the elements that will be automatically included in the help file. Keep the default options and go to the next step.
     

     	Note	If the application already contains a help system, you can use it and include the new features page in it.
  7. Validate the message and the help file save window.
  8. The executable is automatically created (with the options defined when creating the first executable) as well as the help system. You can enter specific information in the help system. In this case, keep the default information. To resume the creation of the setup program, click , which corresponds to "Continue the creation of the setup procedure".
     
     The help is automatically compiled.
  9. Let's now go to the "Setup" section of the wizard. In this first screen, choose the setup mode:
     • Individual setup for an independent application, installed and started on each computer. We will choose this option.
     • Setup with automatic update, for a setup on a server. The applications will be installed from the server. If an update is available, only the server must be updated. The applications installed on the computers will be automatically updated.
     • Setup on a Private Store, to deploy the setup to a previously defined Private Store. Users will be able to install the application from the Store.
     Go to the next step.
  10. Choose a standard setup. Go to the next step.
  11. We will not change the default installation directory. Go to the next step.
  12. Keep the files that appear in the list of installed files. By default, WINDEV shows the Executable file and the help file (created by the new features help). We are going to add the data files:
      • Click "Add". The Windows explorer displays the content of the application generation directory.
      • Select the Customer, Order, OrderLine, PaymentMode and Product data files (files with ".fic", ".ndx" and ".mmo" extension).
      • Validate. The files are automatically saved in the application data directory.
        
  13. Go to the next step.
  14. Uncheck all options from the database parameters. Go to the next step.
  15. Keep the following options in the additional modules:
      
      We will choose the optional tools to install and include the uninstaller. The uninstaller will allow the users to uninstall the application from the Windows program manager. Go to the next step.
      

      	Express	The optional tools are not available in the Express version. In this case, go directly to step 17.
  16. We will select WDOptimizer. This tool optimizes the application data files on a regular basis.
  17. Click "Medium" on the left of the wizard. The setup will be generated in a single directory. By default, the setup program is created in the project "Install" subdirectory. You can:
      • Specify a password for the setup. In this case, only the user who knows the password will be able to install the application.
      • Sign the setup with a certificate. This option is used to ensure the integrity of the setup package.
  18. Validate. The setup program is automatically created.
  19. A window appears, allowing you to test the setup or open the generation directory.

• We will go through the different steps of the "WD Full Application" setup program.
  1. On Windows Vista (or later), a window requests the authorization to run the program. Validate this window.
  2. The setup wizard starts.
     

     	Note	You can change the setup language via a combo box at the upper-right corner of the wizard.

     
     Two setup modes are available:
     • Quick setup: The setup is performed with the parameters specified by the application provider.
     • Custom setup: The wizard asks the user to define the parameters of the application setup.
  3. Choose "Custom setup". The wizard asks for the application installation directory.
     
  4. Keep the default directory and go to the next step.
  5. Finish the application setup wizard.
  6. The application setup starts. Validate the different setup steps.

Overview

• Stand-alone setup:
  This type of setup is used to create a unique setup program. This setup program will be run by the end users from their computers.
  To update the application, you will have to re-create a setup for the application. Then, the end user will have to install this new program.
  This is the type of setup that we have just created.
• Setup with automatic update:
  This type of setup is used to automatically detect the updates when starting the application. If an update is available, users can update immediately.
  This type of setup is available over the network or from the Internet. You can also create a multisite setup.

Setup with update over the network

• the setup of the reference application. The reference application must be installed on the network (in a shared directory or on a server for example), accessible to all the end users of the application.
• the application setup itself. This setup is included in the reference application. It can be accessed once the reference application is installed.

The diagram below presents the setup mode of an application that uses a local HFSQL Classic database, with a network update.

Setup with update from the Internet

• the setup of the reference application and the Web page used to download the client setup. These elements must be installed on an HTTP server.
• the application setup itself. This setup is included in the reference application. It can be accessed once the reference application has been installed, via the download Web page.

The diagram below presents the setup mode of an application that uses an HFSQL Client/Server database, with an internet update.

Multisite setup

• a reference network setup deployed on a local network.
• an HTTP setup used to update the reference setup on the local network.