Resolving Architectural Issues

Neither the Code Advisor nor the Upgrade Wizard is equipped to deal with major architectural issues in your application.

You'll need to carefully evaluate the architectural issues involved in migrating to Visual Basic .NET. If there are major issues involved, you might find that simply rewriting the application in .NET is more efficient than attempting an upgrade. This is particularly true for fat Visual Basic 6.0 client applications that have business logic and data access code intermingled with presentation code.

It's easier to migrate independent classes to Visual Basic .NET than it is to migrate forms, because the forms model in Visual Basic .NET uses completely different technology. Encapsulate your logic in classes, even if the classes are compiled into VB executables along with forms rather than segregated in separate ActiveX components.