Known Problems Upgrading to VB.NET

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   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

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
DDJJ Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 13 December 2004 Status: Offline Points: 143	Post Options Post Reply Quote DDJJ Report Post Thanks(0) Quote Reply Topic: Known Problems Upgrading to VB.NET 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

SuperMario Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 14 February 2004 Status: Offline Points: 18057	Post Options Post Reply Quote SuperMario Report Post Thanks(0) Quote Reply 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.

SuperMario Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 14 February 2004 Status: Offline Points: 18057	Post Options Post Reply Quote SuperMario Report Post Thanks(0) Quote Reply 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.

DDJJ Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 13 December 2004 Status: Offline Points: 143	Post Options Post Reply Quote DDJJ Report Post Thanks(0) Quote Reply 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.

SuperMario Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 14 February 2004 Status: Offline Points: 18057	Post Options Post Reply Quote SuperMario Report Post Thanks(0) Quote Reply 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.

DDJJ Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 13 December 2004 Status: Offline Points: 143	Post Options Post Reply Quote DDJJ Report Post Thanks(0) Quote Reply 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