Upgrading App from version 3.2 to 4

An user 12/15/2009 1:02:22 PM

Hello

I've just purchased the upgrade from your site to version 4.

My VB app has several version 3.2 controls and I'm wondering if there is an weasy way to upgrade my app to replace with version 4.

I can not add version 4 to my project without first removing version 3. I find version 4 has a difference namespace etc so there woudl be a lot of code changes to reference the control.

Any suggestions appreciated.

Regards

Roger

Resolution:

- [SpiceLogic Support Technician] 12/15/2009 7:05:50 PM

Dear Roger,

Thank you for purchasing the upgrade.

Ok, yes, you are right, there are lots of code changes because, namespace, class name and member names are changed. We had reason to change those. Anyway, we can help you about the upgrade.

1. First, make a backup copy of your present application along with the old control dlll (3.2) in case, if you do anything wrong, you can revert back.

2. Then, go to the Form's Designer file something like, myForm.designer.vb. Look for EVERY SINGLE USAGE / REFERENCE of the WInHtmlEDitor Control and TopToolbar / Bottom Toolbar usages and references. Usage and reference means, anywhere you find the object instatiation, or declaration or usage. Then Delete those lines.

3. Then, delete the Old Control reference from your list of references.

4. Delete the Old control from the Visual Studio Toolbox.

5. When you are sure that you got rid of every single line from your Designer file, try to build the application and look into your Form. By this time, you should see error only from your code behind file, not from Designer file. But if you get any error from your xx.Designer.vb file, then, visit the line of the error, and delete that line.

6. Now, Build again and see if you completely removed the old instance from your Form's Designer.vb. The error you get from Code behind file, simply Comment out the lines in the Code behind file which gives error. Finally you should get an error free application where simply the Editor is MISSING.

7. Now, Add a new control to your Visual Studio Toolbox and place a new instance of the new control to your Form.

8. Try to build the application.

9. Now, go to the Code behind file and uncomment the lines where it refered to the editor. Consult the online documentation and find out where is the new equivalent properties and methods. For example, before, you could call Bold method like, editor.Bold(), now it is editor.Operations.Bold(). Most of the properties and methods are just shifted under two major composite properties. "Operations", and "SelectionState". So, from your VS Intellisense, if you check these two properties, you will find all of the old members.

10. Finally, remember to rebind the event handler methods if you handled any event of the control.

If you need any assistance, do let us know.