The Upgrade Wizard was a tool that a company developed for Microsoft and that was included in Visual Studio .NET editions, from version 2002 to 2010. Microsoft ceased to distribute the Upgrade Wizard when support for Visual Basic 6 officially ended. Very few developers missed it, because it never gained a great reputation. Worse, it contributed to create a bad reputation for all VB6-to-.NET code translators on the market.
Unlike the majority of the language conversion products available on the market – which mainly attempt to convert code from one language to another – VB Migration Partner both converts the code *and* uses a support library to decrease the gap between VB6 and VB.NET and to ensure that the converted code truly behaves as expected.
Since its public launch, in May 2008, Code Architects’ VB Migration Partner has proven to be the most complete VB6-to-VB.NET code converter on the market. The power of its code generation engine, which can be easily controller by over 80 different migration pragmas, and the completeness of the companion support library were the winning factors in this market segment.
VB6 and VB.NET are similar languages that differ for a myriad of major and minor details. Even keywords, methods, and controls that have the same name in both environments may have a completely different behavior. The problem is even bigger when converting from VB6 to C#.
Every day we receive requests and queries from VB6 developers and companies who are interested in migrating their code to .NET. Migration a complex application to .NET is a serious matter, therefore it’s no surprise that virtually all our prospects plan to compare our software with the similar tools from the competition.
VB Migration Partner does a superb in dealing with Windows API calls. Here’s a summary of the features that it supports…
VB Migration Partner supports all the controls included in the Visual Basic 6 package, with the only exception of the OLE and Repeater controls. When migrating a form that contains unrecognized 3rd-party (non Microsoft) ActiveX controls, such controls are transformed into “placeholder” controls that appear on the form as red rectangles. For each unrecognized ActiveX control a warning is also generated in the migrated project.
This whitepaper describes the differences between VB6 and .NET controls and the problems you can find in migrating VB6 applications with user-interface. The differences that are common to most controls are described in the All Controls (general) section.