Switching Between Webster Pro Versions

Overview

The Webster Pro Control is released in three functionally identical versions. Each of these has its own file name, object name, set of GUIDs and license string. Demo and beta controls utilize the same object names and GUIDs as the corresponding release versions but use different file names and license strings. Major point version upgrades (e.g. V2.9 to V3.0) are assigned new GUIDs, license strings and file names to avoid version conflicts.

Features

All versions of a given release are identical with regard to properties, methods and events. This means that you can build an application with one version of the control and later easily switch to a different version of the control in the same application. The 32-bit S-Type, 32-bit D-Type and 16-bit D-Type controls can all be installed and registered on the same system at the same time, without conflict. Similar controls with different major version numbers can also be simultaneously installed and registered on a system. For example, you can register and run both a Webster Pro V2.9 and a Webster Pro V3.0 (D-Type) on the same machine.

Procedure: Switching Between Demo/Beta and Release Controls

In a forms-based development environment such as VB, switching from a demo or beta control to an equivalent release version requires updating only the license string. In VB6, the steps to do this are: Run the control setup kit to install the new control on your system. Open your application in VB and display the form containing the control. Note the current control ID (e.g. WebsterPro1) and then delete the control from the form. Insert a new copy of the control in the same place as the previous one. Make sure that the control ID is the same as before (e.g. WebsterPro1) and you should not have to change any code.

Procedure: Switching Between S-Type and D-Type Controls

Many development environments (including VB) will not allow both the D-Type and the S-Type control to be on the project tool palette simultaneously. The following VB6 example steps only require that one of the two be installed at any time: Run the control setup kit to install the new control (the type to which you are switching) on your system. Open your application in VB and note the current control ID (e.g. WebsterPro1), then delete the control from the form. From the VB6 "Project" menu, select "Components...". In the resulting dialog box, uncheck the control type currently used in the project and select the new control type. Insert a new control in the same place as the previous one. Make sure that the control ID is the same as before (e.g. WebsterPro1) and you should not have to change any code.

Procedure: Switching After a Major Point Upgrade

When a major point upgrade is released (e.g. V2.9 to V3.0), you need to rebuild your application if you wish to utilize the new release. The procedure for switching to the new release in VB6 is: Run the control setup kit to install the new release control on your system. Open your application in VB and note the current control ID (e.g. WebsterPro1), then delete the control from the form. From the "Project" menu, select "Components...". In the resulting dialog box, uncheck the old control version currently used in the project and select the new control version (it will have a different name, e.g. Webster Pro Browser Control V3.0). Insert a copy of the new control in the same place as the previous one. Make sure that the control ID is the same as before (e.g. WebsterPro1) and you should not have to change any code.