Geeks With Blogs

News

Google My Blog

Catch me at: The List!


My InstallScript Utility Belt My Amazon Wishlist
My Standard Disclaimer


Archives
Chris G. Williams Beware: I mix tech and personal interests here.

From the "is this really news?" department...

From looking at the currently available versions of 2010, there is no direct upgrade path from VB6 to VS2010. Anyone still using VB6 and wishing to upgrade to VS2010 has two options:  Use the upgrade tool from an earlier version of VS (like 2005 or 2008) and then run the upgrade in VS2010 to get the rest of the way... or rewrite your code.

I'll leave it as an exercise to the reader which is the better option.

I'd like to take a moment to point out the obvious:

A) If you're still using VB6 at this point, you probably don't care about VS2010 compatibility.

B) Running your code through 2 upgrade wizards isn't going to result in anything resembling best practices.

C) Bemoaning the lack of support in 2010 for a 12 year old version of an extinct programming language helps nobody.

This public service announcement is brought to you by the letter C. Thank you.

Posted on Tuesday, March 23, 2010 11:20 AM | Back to top


Comments on this post: No VB6 to VS2010 direct upgrade path

# re: No VB6 to VS2010 direct upgrade path
Requesting Gravatar...
I'm hoping you are joking at the idea that there is even a slight possibility in an automatic upgrade path. :)
Left by Josh Schwartzberg on Mar 24, 2010 9:09 AM

# re: No VB6 to VS2010 direct upgrade path
Requesting Gravatar...
I'm not sure you actually read the post. I'm not advocating automatic upgrades.
Left by Chris G. Williams on Mar 24, 2010 9:43 AM

# re: No VB6 to VS2010 direct upgrade path
Requesting Gravatar...
There sure is an automatic upgrade option.
Download the Visual Basic Upgrade Companion from MSDN
http://msdn.microsoft.com/en-us/vbasic/ff793478
Left by Mauricio Rojas on May 26, 2011 12:21 PM

# re: No VB6 to VS2010 direct upgrade path
Requesting Gravatar...
Technically the VBUC isn't a Microsoft product, nor is it "from MSDN." It's a 3rd party tool being advertised on MSDN. You actually download it from the Artinsoft site.

I stand by the statements I made over a year ago (when this blog post was written.) Running 12 year old code through a converter tool will likely produce unmaintainable crap that your team won't be able to support. If you need to use a conversion tool, you probably don't have the skills to do a proper rewrite, which means you almost certainly won't have the skills to customize the end result.
Left by Chris G. Williams on May 26, 2011 2:29 PM

Your comment:
 (will show your gravatar)


Copyright © Chris G. Williams | Powered by: GeeksWithBlogs.net