Can the convert-test-fix cycle really handle all migration issues?
• Pragmas are usually enough powerful to convert any VB6 application into a VB.NET solution that has no compilation errors. Pragmas are also useful to get rid of most runtime errors and misbehaviors, but realistically they can’t solve all the problems that might occur after the conversion. For example, pragmas can’t help if the original application uses the DataReport designer or one or more unrecognized ActiveX controls. In such cases, you must manually fix the converted VB.NET application. If you postpone such manual fixes at the end of the automatic conversion process you can reduce to the minimum the period during which the original VB6 and the converted VB.NET applications are out-of-sync.
