I need to extend and improve the VB6 application while the migration process proceeds. Does VB Migration Partner handle such a requirement?
• All the other migration tools we are aware of force you to work on a “snapshot” of the original VB6 application; if you later extend or modify the VB6 code, the converted VB.NET application won’t include all these fixes and enhancements. If the migration process takes weeks or months – quite a reasonable assumption for real world business applications – the neat result is that the VB.NET application is already outdated by the time it finally compiles and runs correctly. VB Migration Partner copes with this issue by introducing the concept of convert-test-fix cycle.