A common mistake I have seen when teams use automated migration tools is the failure to consider our old friend GIGO – Garbage In, Garbage Out.
Before you consider using any automated tool such as the Visual Basic Upgrade Wizard you should spend some time tidying up your VB6 application to minimize the amount of post upgrade work and give the tool the best chance of success.
Helpful resources include:
- Things to Consider Before Upgrading
- Preparing a Visual Basic 6.0 Application for Upgrading
- Language Recommendations for Upgrading which has some great advice. e.g. Use Early Binding and Explicit Conversions
There appear to be a couple of minor inconsistencies in the documentation. The Printer object, the PrintForm method and the Line and Shape controls are now supported by the Visual Basic 2008 upgrade wizard.