VWG,

Is there a post for a preferred upgrade path between 6.3.x and 6.4.x. I've recently updated to 6.4 and have many issues.  

I've been working on a product for over a year now and have been using 6.3.6. It's buggy but I've developed a series of work arounds and have a somewhat stable app that is about 75% done. Recently I built a new VM and installed 6.4. I copied all my 6.3 projects over to my new VM and opened them up to find that they wont compile and run.

It seems you have changed the object model on many of the controls. The toolbar is one example, the datagrid is another. So much for backward compatibility. Thats a dirty little secret.

I've been able to get one small user control to actually compile and run by commenting out a bunch of needed code. I'll deal with that later. After a lot of pain I finally realized that I needed to change/add a theme. The 6.3 settings made 6.4 blow its mind. Then after a clean compile Ive been playing with all the shipped themes and they all look terrible. Each has its own reason why I wouldn't use it in real life. I also noticed it's much slower than 6.3.x.

I must be missing something because I doubt the product is this bad, it must be me.

What are the recommended steps for 6.3 apps to be updated to 6.4. Do I installed 6.4 over 6.3 or start a fresh development machine like I did. Do I just open and compile 6.3 apps in 6.4 or is there a conversion that must be run. You can't possibly expect me to start 6.4 apps from scratch. 

Thx,

Dan

Hello Dan,

Within a couple of weeks we will publish a detailed walkthrough article to describe the all the possible changes required when migrating your application from VWG v6.3 to v6.4.
This article will have an application attached in two states - one is the Original VWG v6.3 application and the other is the v6.4 application after changes made.
The article will also include a short code example for every change required.

There are currently two articles that may be of interest to you. They may help you until we release the previously discussed article is published. you can find them here:
http://wiki.visualwebgui.com/pages/index.php/Changelogs
http://wiki.visualwebgui.com/pages/index.php/Upgrading_to_Visual_WebGui_v6.4_-_Changes_%26_Requirements


Much work is being done now on the Visual WebGui ready-made Themes. These thoroughly fixed themes will be deployed with VWG v6.4 Beta2 installation (the next VWG v6.4 version to be released).
I would greatly appreciate it if you could re-evaluate them at that point to see if things have improved enough for you to be able to use any of them in your application.


Regarding your reoprt of VWG v6.4 slowness, please view Itzik's post in this thread here.

Regards,

Ori Cohen
Support Manager, the Visual WebGui team

Hi Dan,

Sorry for the long wait for a reply. We are still working on an upgrade document, but I thought I would respond to your specific points in any case.

2) The tiny ToolBar height has been fixed in post 6.4.0Beta1c codebase. See this thread here.

3) You are correct about the ToolBar EventArg changes. This has been discussed multiple times on the forums and is explained in the breaking changes documentation on the wiki here. The reason being that the Click event on the ToolBar itself is now for the ToolBar only, but not it's buttons where you would use ToolBar.ButtonClick.

4) I would like more specifics on this. Do you mean there is a property name(s) that is not supported on 6.4 but where supported on 6.3, or do you mean that the functionality is not there any more. Please explain.

5) I assume you are refering to the theme samples, downloadable seperately, right ? If so, then these themes are from a very early stages of version 6.4 and they do need an update and they will be in due time.

6) Can you please clarify if you are comparing to a version 6.3.x performance here, or if you mean this just as a general statement for the DataGridView? In any case, a major effort has been made in the upcoming Beta2 release for performance so I am sure you will get a much better performance once Beta2 is out.

7. I must admit that I have never noticed this. Did this not occur on 6.3? Any situation more than others that will show this message?

8. I again reference the Wiki breaking changes article. If you do have some more compile errors please let us know the specifics so we can add them to the list.

Thank you very much for your notes.

Palli