PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

  • Overview
  • Updating components and deployed executables
  • The different methods
  • Sharing a component between several applications
  • Forcing the use of an external component when the WDK was included in the application
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 method for deploying an application that uses one or more external components is the same as the method for deploying a standard application ("Project .. Create the setup program").The method for deploying an application that uses one or more external components is the same as the method for deploying a standard application: on the "Project" pane, in the "Generation" group, expand "Setup procedure" and select "Create the setup procedure". ).
When deploying an application that contains a component, the following files are automatically installed on the user computer (or on the server):
  • <ComponentName>.WDK
  • <ApplicationName>.EXE
    WEBDEV - Server code This file is not installed.
  • the files required for the component and for the application to operate.
Updating components and deployed executables
When updating a component and/or a deployed executable, you have the ability to install on the end-user computer:
  • the application executable, the component and the files required for them to operate.
  • the application executable and the files required for the application to operate.
  • the component and the files required for the component to operate.

The different methods

Two methods can be used to update a component on the end-user computers:
  1. Recompiling the host project
    Recompile the application that is using the component and redistribute the application with the component. In this case, no version problem or compatibility problem will occur. The recompilation is required in the following cases:
    • New functions have been added to the component and they must be taken into account by the application.
    • The parameters of some procedures have been modified.
    • Incompatibility between the new version and the earlier versions of the component.
    • ...
  2. Distributing the .WDK file directly
    Provide an upgraded version of component (.WDK file) to the end users without recompiling the project. In most cases, this possibility applies when:
    • The new version is used to correct the problems of an earlier version.
    • New features have been added into the component but they are not required to run the application.
Sharing a component between several applications
Several applications installed on the same computer can use the same external component. To share the component among these applications and to avoid duplicating the component in each application, perform the following operations:
  1. Copy the component files into a directory:
    • the <ComponentName>.WDK file
    • the other component files (if necessary)
  2. In each directory of the applications that use the component:
    • Delete <ComponentName>.WDK and the files required by the component from the application directory.
    • Create a <ComponentName>.INI file in the application directory. This file has the following structure:
      [General]
      Location = <Directory in which the component files are available>
Benefit: The update of the external component is easier: it is performed in the component directory only (and not in each application). If the component is also found in the application directory, if a .INI file is found, the component specified in the .INI file has priority.
Forcing the use of an external component when the WDK was included in the application
Versions 15 and later
When a component was included in the library of an application when the executable was created, you still have the ability to force the use of an external WDK.
This enables you for example to debug the component or to correct a feature without having the project of the application.
To do so:
  1. Create a file named <Component name>.ini beside the executable of the application.
  2. This file has the following structure:
    [Debug]
    Localization = <Path of WDK to use>
New in version 15
When a component was included in the library of an application when the executable was created, you still have the ability to force the use of an external WDK.
This enables you for example to debug the component or to correct a feature without having the project of the application.
To do so:
  1. Create a file named <Component name>.ini beside the executable of the application.
  2. This file has the following structure:
    [Debug]
    Localization = <Path of WDK to use>
When a component was included in the library of an application when the executable was created, you still have the ability to force the use of an external WDK.
This enables you for example to debug the component or to correct a feature without having the project of the application.
To do so:
  1. Create a file named <Component name>.ini beside the executable of the application.
  2. This file has the following structure:
    [Debug]
    Localization = <Path of WDK to use>
Minimum required version
  • Version 9
This page is also available for…
Comments
Click [Add] to post a comment