PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US
  • Overview
  • How to proceed?
  • Generating an application in Universal Windows 10 App mode
  • Generating and deploying the application
  • Generating the application for Windows Store
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
Generating an application for Universal Windows 10 App
Overview
The generation of an application in Universal Windows 10 App mode groups all the project elements (windows, code, etc.) in an archive in order for the application to be deployed on a Windows 10 device and to be distributed.
How to proceed?

Generating an application in Universal Windows 10 App mode

To generate an application in Universal Windows 10 App mode:
  1. Click among the quick access buttons. The wizard for generating the application in Universal Windows 10 App mode starts.
    Note: If all the modules required to generate an application in Universal Windows 10 App mode are not installed, the wizard indicates the missing elements. See Required configuration for more details.
  2. Select the generation mode:
Caution: The development of applications in Universal Windows 10 mode is available for test in this version. We advise you not to distribute the applications on the stores.

Generating and deploying the application

The generation wizard then the deployment wizard are started.
The different steps of the generation wizard are as follows:
  1. Specify the general information about the application:
    • Application name,
    • Application description,
    • Software publisher
    • Copyright.
  2. Go to the next step.
  3. Specify the version number of the application in standard format. This format corresponds to a set of 4 numbers separated by dots.
    • The first group of 4 digits corresponds to the number of major changes performed in the application.
    • The second group of 4 digits corresponds to the number of minor changes performed in the application.
    • The third group of 4 digits corresponds to the generation number.
      We advise you to automatically increment this number at each generation. This increment operation is automatically performed if "Automatically increment the version at each generation" is checked.
    • The last group of 4 digits corresponds to the number of reviews (branches in the SCM for example).
  4. Go to the next step.
  5. Choose the different images associated with the application. By default, WINDEV Mobile generates images to the expected format. You can customize these images or use your own images.
    The expected images are:
    • The standard logo of the application for the square tile (150 x 150 pixels)
    • The small logo for the square tile and the list of all applications (44 x 44 pixels)
    • The logo for the square tile (71 x 71 pixels)
    • The logo for the square tile (310 x 310 pixels)
    • The large application logo for the rectangular tile (310 x 150 pixels)
    • The small logo for the task manager, the thumbnails and the notification toasts (30 x 30 pixels)
    • The image of splash screen (620 x 300 pixels)
    • The image of the application displayed in Windows Store (50 x 50 pixels)
      Tip: you have the ability to select an image in the image catalog of WINDEV Mobile. The expected images will be automatically generated from the selected image and the corresponding files will be associated in the wizard.
  6. Go to the next step.
  7. Choose:
    • the background color of the tile.
    • the display mode of the tile.
  8. Go to the next step.
  9. 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. Go to the next step.
  10. Specify whether files must be included in the package. You have the ability to include:
    • specific resources.
    • specific images.
    • data files.
  11. Specify the "Write" option:
    • If the "Write" option is checked for the files, these files will be automatically checked out (files that must be modified by the application for example). In this case, specify the application directory into which this file must be checked out (data directory by default).
    • If the "Write" option is unchecked for the files, these files can be:
      • used directly (files to read for example: sound files, image files, ...). These files are included in the application and they will not be checked out. fResourceDir is used to access these files in read-only.
      • checked out by programming with fExtractResource.
  12. Go to the next step.
  13. If your project contains several languages, specify the languages found in the application. Go to the next step.
  14. Select the features used by the application.
    Note: If you are using features linked to APIs, the next step allows you to declare the files used by the APIs and their characteristics.
  15. Go to the next step.
  16. The signature of the application is mandatory. The wizard proposes to generate a certificate or to use an existing certificate. In this last case, all you have to do is select the requested certificate.
    To generate a new certificate:
    • Specify the name of certificate to generate.
    • The next wizard step is used to create the certificate.
      • Click the "Create the certificate" button.
      • The Windows explorer displays the created certificate.
      • In the explorer, display the popup menu of file (right mouse click) and select "Install the certificate". The wizard for importing the certificate starts.
      • In the wizard, select the storage location: "Local computer". Click "Next".
      • Select "Place all certificates in the following store".
      • Click the "Browse" button and select the "Trust root certification authorities" store.
      • Click the "Next" button until the end of the wizard. A message is displayed, indicating that the import was successful.
    • In the wizard, check "The certificate was successfully installed" and go to the next step.
  17. The screen for generating the application is displayed. In this screen, you have the ability to declare a "windows.protocol" extension. A "Windows protocol" extension is used to start the application:
    • via a command line (press Windows + R simultaneously and run the interpreter of commands by typing "CMD").
    • from a browser.
      To declare a "windows.protocol" extension:
      • Click the "Advanced" button,
      • In the window that is opened, enter the name that must be given to the protocol. The command line and the URL for the browsers are automatically created.
    • For example, if the protocol is named "wdorganizer", the following syntaxes will be generated:
      • for a start in command line: "start wdorganizer:"
      • for a start from a browser: "wdorganizer:"
  18. Validate the generation of the Universal Windows 10 App application.
  19. The deployment wizard starts and proposes to select the deployment platform:

Generating the application for Windows Store

Caution: The development of applications in Universal Windows 10 platform mode is available for test in this version. We advise you not to distribute the applications on the stores.
The different wizard steps are as follows:
  1. Specify the general information about the application:
    • Application name,
    • Application description,
    • Software publisher
    • Copyright.
  2. Go to the next step.
  3. Specify the specific information for the deployment on Windows Store:
    • Developer account: This information is identical to the one given when creating a Microsoft developer account.
      • Full name of the application publisher.
      • Identifier of the application publisher.
    • Application name reserved in Windows Store.
    • Full name of application package.
    See Deploying on Windows Store for more details.
  4. Go to the next step.
  5. Specify the version number of the application in standard format. This format corresponds to a set of 4 numbers separated by dots.
    • The first group of 4 digits corresponds to the number of major changes performed in the application.
    • The second group of 4 digits corresponds to the number of minor changes performed in the application.
    • The third group of 4 digits corresponds to the generation number.
      We advise you to automatically increment this number at each generation. This increment operation is automatically performed if "Automatically increment the version at each generation" is checked.
    • The last group of 4 digits corresponds to the number of reviews (branches in the SCM for example).
  6. Go to the next step.
  7. Choose the different images associated with the application. By default, WINDEV Mobile generates images to the expected format. You can customize these images or use your own images.
    The expected images are:
    • The standard logo of the application for the square tile (150 x 150 pixels)
    • The small logo for the square tile and the list of all applications (44 x 44 pixels)
    • The logo for the square tile (71 x 71 pixels)
    • The logo for the square tile (310 x 310 pixels)
    • The large application logo for the rectangular tile (310 x 150 pixels)
    • The small logo for the task manager, the thumbnails and the notification toasts (30 x 30 pixels)
    • The image of splash screen (620 x 300 pixels)
    • The image of the application displayed in Windows Store (50 x 50 pixels)
      Tip: you have the ability to select an image in the image catalog of WINDEV Mobile. The expected images will be automatically generated from the selected image and the corresponding files will be associated in the wizard.
  8. Choose:
    • the background color of the tile.
    • the display mode of the tile.
  9. Go to the next step.
  10. 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. Go to the next step.
  11. Specify whether files must be included in the package. You have the ability to include:
    • specific resources.
    • specific images.
    • data files.
  12. Specify the "Write" option:
    • If the "Write" option is checked for the files, these files will be automatically checked out (files that must be modified by the application for example). In this case, specify the application directory into which this file must be checked out (data directory by default).
    • If the "Write" option is unchecked for the files, these files can be:
      • used directly (files to read for example: sound files, image files, ...). These files are included in the application and they will not be checked out. fResourceDir is used to access these files in read-only.
      • checked out by programming with fExtractResource.
  13. Go to the next step.
  14. If your project contains several languages, specify the languages found in the application. Go to the next step.
  15. Select the features used by the application.
    Note: If you are using features linked to APIs, the next step allows you to declare the files used by the APIs and their characteristics.
  16. Go to the next step.
  17. The signature of the application is mandatory. The wizard proposes to generate a certificate or to use an existing certificate. In this last case, all you have to do is select the requested certificate.
    To generate a new certificate:
    • Specify the name of certificate to generate.
    • The next wizard plane is used to create the certificate.
      • Click the "Create the certificate" button.
      • Validate the setup of certificate on the current computer.
    • The Windows explorer displays the created certificate.
      • In the explorer, display the popup menu of file (right mouse click) and select "Install the certificate". The wizard for importing the certificate starts.
      • In the wizard, select the storage location: "Local computer". Click "Next".
      • Select "Place all certificates in the following store".
      • Click the "Browse" button and select the "Trust root certification authorities" store.
      • Click the "Next" button until the end of the wizard. A message is displayed, indicating that the import was successful.
    • In the wizard, check "The certificate was successfully installed" and go to the next step.
  18. The screen for generating the application is displayed. In this screen, you have the ability to declare a "windows.protocol" extension. A "Windows protocol" extension is used to start the application:
    • via a command line (press Windows + R simultaneously and run the interpreter of commands by typing "CMD").
    • from a browser.
      To declare a "windows.protocol" extension:
      • Click the "Advanced" button,
      • In the window that is opened, enter the name that must be given to the protocol, the command line and the URL for the browsers are automatically created.
    • For example, if the protocol is named "wdorganizer", the following syntaxes will be generated:
      • for a start in command line: "start wdorganizer:"
      • for a start from a browser: "wdorganizer:"
  19. Validate the generation of the Universal Windows 10 App application. The <AppName>.appxbundle file is generated at the end of wizard. This file must be uploaded onto the submission Web site. See Deploying on Windows Store for more details.
Minimum required version
  • Version 21
This page is also available for…
Comments
Click [Add] to post a comment