Suite Pro - Known Problems Upgrading to VB.NET

Print Page | Close Window

Known Problems Upgrading to VB.NET

Printed From: Codejock Forums
Category: Codejock Products
Forum Name: Suite Pro
Forum Description: Topics Related to Codejock Suite Pro
URL: http://forum.codejock.com/forum_posts.asp?TID=5104
Printed Date: 17 November 2024 at 5:39am
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com

Topic: Known Problems Upgrading to VB.NET

Posted By: DDJJ
Subject: Known Problems Upgrading to VB.NET
Date Posted: 20 September 2006 at 10:35am

We are considering upgrading (maybe the wrong word to use) our VB6 app to VB.NET 2005. Since a lot of the code in our app relates to codejock controls, can anyone point out specific problems we might have after upgrading (if any??)? I'm mostly concerned that a lot of the codejock related code will (for whatever reason) need to be rewritten after the change.

Thanks for any feedback.

Dan

Replies:

Posted By: SuperMario
Date Posted: 20 September 2006 at 10:43am

should be an easy conversion. you can look at some of the VB6 and VB.net samples to compare how little the syntax has changed.

Posted By: SuperMario
Date Posted: 20 September 2006 at 10:51am

Some of the biggest things, which are really minor would be the name of event parameters changed, for example the Commandbars Execture event in VB6 has a "Control" parameter, where it is now "eventArgs.control" in VB.NET. You don't use the keyword "Set" like you did in VB6, and you might need to fully qualify names such as "XtremeCommandBars.XTPControlType.xtpControlButton" which you can use Imports\Using statement (can't remember which is for vb and c#) to cut down on some of the name.

The only other thing is that some of the popup control properties are automatically renamed because they had the same name as the inherited control, so the codejock version will start with a "ctl" or something like that.

Posted By: DDJJ
Date Posted: 20 September 2006 at 12:14pm

Thanks for the detailed response, SuperMario.

At a minimum, it sounds like there will be some time required to bring the cj control code up to speed. Now, if I could only come up with an accurate estimate of the total time needed to convert all controls in the app, plus whatever other problems crop up.

Cheers.

Posted By: SuperMario
Date Posted: 20 September 2006 at 3:01pm

I forgot one important thing, SkinFramework only works with VB6, it will not work in VS2005. But not a big deal if you don't use it.

Posted By: DDJJ
Date Posted: 20 September 2006 at 4:24pm

Thanks. I had already noted that from another thread, but at least for now it's not relevant since we're not using it.

I also saw the thread about coming out with a .NET version of the controls. Will monitor as it develops.

Dan