It isn’t difficult! Only three steps are required to transition from a Webster (or WebTrek or WebViewer) to a Webster Pro.
Delete the old control from your form and insert a Webster Pro in its place. You can keep the control ID the same as it was (e.g. WebsterCtrl1) to minimize code changes.
If you create the control directly (rather than in a design-time form), change the class ID string from “Webster.WebsterCtrl.1” to “Webster.WebsterPro.1”.
The DoClickURL event has been removed, so if you handled that event you will need to move the code from the DoClickURL handler to a BeforeNavigate event handler. A simple cut-and-paste should be sufficient in most cases.
Note that unlike the old DoClickURL event, BeforeNavigate is fired for all navigation actions including container navigation requests (via the Navigate method, assignment to the PageURL property etc.). You can determine whether a BeforeNavigate event is the result of a container action by inspecting the NavContainerAction bit in the event’s NavFlags argument.
The archaic LoadComplete event has been removed. Any code in a LoadComplete event handler should be moved to the PageStatusChange event handler. Since PageStatusChange is called for status conditions other than load completion, you can surround the code with a test for the Status argument matching a completion status.
That’s it! No other actions are required for upgrading to a Webster Pro, although you may want to take advantage of the many new properties, events and methods.