1. If you know you want to migrate your Visual Basic 6 application to VB.NET, what is the first thing you should do?
A) Open the Visual Basic Upgrade Wizard, get a cup of coffee and watch it run.
B) Assess the VB 6 application; find out what controls it uses, what projects are in there and so on.
C) Cancel all social plans for the next couple months and start rewriting the app in .NET.
D) Schedule meetings with end users to see what features they want to add to the app.
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
You may be tempted to go straight to the Upgrade Wizard, but doing so will bring up a lot of warnings. You may decide to add functionality to the application while you're migrating it, but that opens a large can of worms. And why start over in .NET when much of your VB 6 application will likely work just fine? As indicated in the SearchVB.com tip, Getting started: Tips for VB6 to VB.NET 2.0 migration, the first thing to do when considering a VB 6-to-VB.NET migration is taking a good, hard look at what you have.