Clarion Community Help

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
| **Navigation:**  [[guide to the clarion examples.htm|Guide to Examples]] >====== Using the Clarion Version Resource Template in a Multi-Application Setting ====== | [[thread model example.htm|{{btn_prev_n.gif|Previous page}}]][[guide to the clarion examples.htm|{{btn_home_n.gif|Return to chapter overview}}]][[xml parsing example.htm|{{btn_next_n.gif|Next page}}]] |
|  ||

**The Version Resource Template is an easy to use global extension template for adding standard product information and version stamping to your applications. An optional feature of the template is that you can select an external resource file to be used, providing a mechanism to stamp "Product family" information across multiple applications.**

**This topic will guide you through the very simple steps required to apply the shared information from a single application to others in the product. Note that the specific build number may change from those shown.**

The example files are located in //..\Clarion7\examples\versionres//. The three application files used are DATA.APP, CODE.APP and MAINAPP.APP. The DATA.APP contains all File and Class declarations as well as holding the project where the "Product" information is maintained in the Global Version Resource template. The CODE.APP is merely a source code application with a single procedure and uses the external "Product" information maintained by the DATA.APP file. Finally the MAINAPP.APP is the executable that incorporates the other DLLs and uses the external "Product" information maintained by the DATA.APP file.

First let's open the DATA.APP and go to the Global Extensions and select the **Product Version** tab

{{vrex1.jpg|VREx1.jpg}}

The information entered on this tab is the "Product family" information that can be shared with other applications. When we compile the application and examine the details of the DLL (RIGHT-CLICK on the DLL in the Windows Explorer, and select Properties) we can see it displayed like this:

{{vrex2.jpg|VREx2.jpg}}

Note that the **Product Version** entry is not the same as the **File Version** shown at the top of the dialog. The **File Version** is information about //this// specific resource.

This screenshot displays the **Product Name:**

{{vrex3.jpg|VREx3.jpg}}

Open the CODE.APP file and go to the Global Extensions and select the **Product Version** tab of the Version Resource template, which should look like this:

{{vrex4.jpg|VREx4.jpg}}

Note that we have selected the "Use External Product Information" checkbox and the used the ellipses button to select the "data.version" file.

After building the DLL we can examine the properties and see that the **Product Version** is the same as the DATA.DLL file.

{{vrex5.jpg|VREx5.jpg}}

And that the **Product Name** matches as well

{{vrex6.jpg|VREx6.jpg}}

Repeat the same steps for the MAINAPP.APP file as used in the CODE.APP file and it will contain the same **Product Version** and **Name** as the DATA.DLL file:

{{vrex7.jpg|VREx7.jpg}}

Again, the **Product Name** for the MAINAPP is shown below:

{{vrex8.jpg|VREx8.jpg}}