I have never used Visual Basic in my life and can only guess how much pain it must be for those who have to maintain VB6 applications after Microsoft abandoned the product. Fortunately for those developers, there are tools that can help with the migration to other platforms. I recently came along VB Migration Partner, a new tool that automatically translates VB6 applications to VB.NET. Judging by the feedback of beta testers I read, it does a very good job of translating the various VB6 quirks to VB.NET. Have you used such a tool in the past? Are there better alternatives like migrating to Delphi?
-
-
About
This is a blog by Dennis & Tobias
Gurock – Directors at Gurock Software,
a software company specialized in
software development tools. -
Subscribe
Links
Categories
- Books (2)
- Business (31)
- Delphi (58)
- Development (31)
- General (34)
- Gurock Software (54)
- Marketing (3)
- Other ISVs (14)
- SmartInspect (92)
- SmartInspect 2.0 (6)
- SmartInspect 3.0 (13)
- SmartInspect EAP (3)
- VMware (8)
- Websites (23)
Archives
- August 2008 (7)
- July 2008 (7)
- June 2008 (3)
- May 2008 (3)
- April 2008 (4)
- March 2008 (1)
- February 2008 (4)
- January 2008 (1)
- December 2007 (4)
- November 2007 (1)
- October 2007 (3)
- September 2007 (5)
- August 2007 (6)
- July 2007 (1)
- June 2007 (4)
- May 2007 (4)
- April 2007 (4)
- March 2007 (4)
- February 2007 (3)
- January 2007 (4)
- December 2006 (8)
- November 2006 (4)
- October 2006 (4)
- September 2006 (4)
- August 2006 (9)
- July 2006 (4)
- June 2006 (5)
- May 2006 (3)
- April 2006 (3)
- March 2006 (6)
- February 2006 (9)
- January 2006 (4)
- December 2005 (6)
- November 2005 (11)
- October 2005 (14)
- September 2005 (10)
- August 2005 (17)
- July 2005 (14)
2 Comments
Thank you for mentioning our tool, Dennis.
Let me add just one thought. Code conversion tools, especially VB6-to-VB.NET tools, suffer from a bad reputation of not being enough powerful or cost-effective. To counter this bad reputation we made the *COMPLETE* documentation and knowledge base available to anybody, at http://www.vbmigration.com.
Even better, we have uploaded tons of VB6 code samples paired with the corresponding VB.NET code that our VB Migration Partner generates, so that readers can see by themselves. Notice that these samples are real-world open source projects found on the Internet, rather than artificially built code examples that carefully highlights our tool’s strengths and hide its weakness.
As far as I know, no other vendor has take a similar candid approach, at least not to this extent, presumably because they can’t offer such a high success ratio without in-depth edits to either the original VB6 code or the generated VB.NET code. Looking at the great response both during the beta test period and after the official launch, it is evident that the developer community appreciates this transparency.
Your last question - Are there better alternative like migrating to Delphi? - calls for a more detailed answer. I will reply on my own blog, at http://www.vbmigration.com/blog
thanks again,
Francesco Balena
The VB Migration Partner Team
Thanks for the detailed comment Francesco. I really like the open and transparent approach you are taking and I’m sure that prospective users will reward it.