|
|
|
|
|
|
|
|
|
|
- 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
Deploying an application that uses an external component
Deploying an application using one or more external components is done in the same way as deploying a conventional application: under the "Project" pane, in the "Generation" group, pull down "Setup procedure" and select "Create installation procedure".. When deploying an application that contains a component, the following files are automatically installed on the user computer (or on the server): - <Component name>.WDK
- <ApplicationName>.EXE
 This file is not installed. - the files required for the component and the application.
Updating components and deployed executables When updating a component and/or an executable, the following elements can be installed on the end-user computer: - the application executable, the component and the necessary files.
- the executable and the files required for the application.
- the component and any necessary files.
The different methods Two methods can be used to update a component on the end-user computers:
- Recompiling the host project
Recompile the application that uses 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 new and earlier versions of the component.
- ...
- Distributing the .WDK file directly
Deliver a component update (.WDK file) directly to customers without recompiling the project.. In most cases, this possibility applies when:- The new version is used to correct problems of an earlier version.
- New features have been added to the component but 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: - Copy the component files into a directory:
- the <Component name>.WDK file
- the other component files (if necessary)
- In each directory of applications that use the component:
- Delete <Component name>.WDK and the files required by the component from the application directory.
- Create a <Component name>.INI file in the application directory. This file has the following structure:
[General]
Localisation = <Répertoire dans lequel les fichiers du composant sont disponibles>
Advantage: External component updates are made easier: they are carried out only in the component directory (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 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: - Create a file named <Component name>.ini beside the application executable.
- This file has the following structure:
[Debug]
Localisation = <Chemin du WDK Ã utiliser>
This page is also available for…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|