What is the convert-test-fix cycle?
• Typically, migrating a real-world VB6 application is an iterative process that goes through the following three stages. First, you convert the original VB6 code and test the result; odds are that the converted VB.NET project contains invalid code that causes compilation errors, thus you must understand how to fix the original code to avoid these errors. However, instead of modifying the VB6 application or the converted VB.NET application, VB Migration Partner allows you to just add one or more pragmas to the original VB6 code: pragmas are just remarks, therefore they can’t affect the way the VB6 application works. You can then re-submit the “pragma-enhanced” VB6 project to VB Migration Partner, see the results, and add more pragmas if necessary, and continue this process until no more compilation errors occur. When the converted VB.NET project compiles correctly you are now at about the middle of the migration process, because you can now actually run the VB.NET project and see how i
