Codejock Developer Community : Known Problems Upgrading to VB.NET http://forum.codejock.com/ Copyright (c) 2006-2013 Web Wiz Forums - All Rights Reserved. Thu, 23 Jul 2026 06:23:51 +0000 Wed, 20 Sep 2006 16:24:17 +0000 http://blogs.law.harvard.edu/tech/rss Web Wiz Forums 12.04 360 forum.codejock.com/RSS_post_feed.asp?TID=5104 <![CDATA[Codejock Developer Community]]> http://forum.codejock.com/forum_images/codejock-logo.gif http://forum.codejock.com/ <![CDATA[Known Problems Upgrading to VB.NET : Thanks. I had already noted that...]]> http://forum.codejock.com/forum_posts.asp?TID=5104&PID=15942&title=known-problems-upgrading-to-vb-net#15942 Author: DDJJ
Subject: 5104
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
 
]]> Wed, 20 Sep 2006 16:24:17 +0000 http://forum.codejock.com/forum_posts.asp?TID=5104&PID=15942&title=known-problems-upgrading-to-vb-net#15942 <![CDATA[Known Problems Upgrading to VB.NET : I forgot one important thing,...]]> http://forum.codejock.com/forum_posts.asp?TID=5104&PID=15940&title=known-problems-upgrading-to-vb-net#15940 Author: SuperMario
Subject: 5104
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.]]> Wed, 20 Sep 2006 15:01:32 +0000 http://forum.codejock.com/forum_posts.asp?TID=5104&PID=15940&title=known-problems-upgrading-to-vb-net#15940 <![CDATA[Known Problems Upgrading to VB.NET : Thanks for the detailed response,...]]> http://forum.codejock.com/forum_posts.asp?TID=5104&PID=15932&title=known-problems-upgrading-to-vb-net#15932 Author: DDJJ
Subject: 5104
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.
 
]]> Wed, 20 Sep 2006 12:14:36 +0000 http://forum.codejock.com/forum_posts.asp?TID=5104&PID=15932&title=known-problems-upgrading-to-vb-net#15932 <![CDATA[Known Problems Upgrading to VB.NET : Some of the biggest things,...]]> http://forum.codejock.com/forum_posts.asp?TID=5104&PID=15926&title=known-problems-upgrading-to-vb-net#15926 Author: SuperMario
Subject: 5104
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.
]]> Wed, 20 Sep 2006 10:51:48 +0000 http://forum.codejock.com/forum_posts.asp?TID=5104&PID=15926&title=known-problems-upgrading-to-vb-net#15926 <![CDATA[Known Problems Upgrading to VB.NET : should be an easy conversion....]]> http://forum.codejock.com/forum_posts.asp?TID=5104&PID=15923&title=known-problems-upgrading-to-vb-net#15923 Author: SuperMario
Subject: 5104
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.]]> Wed, 20 Sep 2006 10:43:54 +0000 http://forum.codejock.com/forum_posts.asp?TID=5104&PID=15923&title=known-problems-upgrading-to-vb-net#15923 <![CDATA[Known Problems Upgrading to VB.NET : We are considering upgrading (maybe...]]> http://forum.codejock.com/forum_posts.asp?TID=5104&PID=15922&title=known-problems-upgrading-to-vb-net#15922 Author: DDJJ
Subject: 5104
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
 
 
]]> Wed, 20 Sep 2006 10:35:57 +0000 http://forum.codejock.com/forum_posts.asp?TID=5104&PID=15922&title=known-problems-upgrading-to-vb-net#15922