Migrating from VB6 to VB.NET with Project Analyzer
Project Analyzer Enterprise Edition can review classic VB6 code for upgrade incompatibilities with .NET. Review compatibility issues and fix them before migrating your code to VB.NET.
Get prepared and save migration work
Planning to move code from VB6 to VB.NET? Get ready for a challenge! Upgrading to VB.NET is not just a matter of loading your existing code in it. Simply put, your code won't run without changes. It's essential to prepare your code before you migrate it.
You can easily start the preparations today. It makes sense to write .NET compatible code even if you're planning to stay in VB6 for a while.
Read more: 10 Steps to migrate existing code to VB.NET
Project Analyzer helps you migrate
Project Analyzer Enterprise Edition provides several tools that help you prepare your existing code for VB.NET. Among the most useful features are automatic dead code removal and VB.NET Compatibility Check.
Problem categories detected by VB.NET Compatibility Check
The VB.NET Compatibility Check feature analyzes your existing Visual Basic code to find features and syntax conventions that have changed in VB.NET. When it finds an incompatibility, it marks the location with a problem icon in one of the following categories.
Getting prepared in advance
Not upgrading to VB.NET yet? Then it's even more important to know a little about VB.NET. With a minimum effort, you can write more .NET compatible code. When you upgrade, you have a few less things to worry about.
Download and try it now for free
Download the Project Analyzer demo. Open the Options menu, select Problem Options and enable a VB.NET related problem filter. Take a peek in the Add-ins|Enterprise Edition menu to see a compatibility report.
Project Analyzer supports VB.NET code analysis as a standard feature. In addition to .NET, it also supports all Visual Basic versions from 3.0 to 6.0.
If you are preparing your VB6 apps for migration to .NET this tool is also very helpful, because it can automatically spot most VB6 language elements that the Update Wizard doesn't convert correctly to VB.NET.
If you first use Project Analyzer to detect .Net incompatibilities in your Visual Basic 6 program and then fix them, you are likely to have better results when you run the migration wizard.
Peter Aitken at DevSource.com