Footnotes ,  and  are interesting:
In response, the Visual Basic user community expressed its grave concern and lobbied users to sign a petition to keep the product alive. Microsoft has so far refused to change their position on the matter.
We're talking about the difficulty to migrate existing code in VB6 back in 2002 and that it was recommended 12 years ago that folks "learn VS.Net first".
Zoufaly will not tell you that migrating VB6 to VB.NET is in any way easy. It is not in his nature to lie. He is more of a developer turned executive rather than the other way around. He seems vaguely nonplussed by his newfound stature in the development world. Talking to him last week at VSLive!, he gave a very candid appraisal of the technology his company has created and the challenges which are inherent in migration—both the ones that his tool can solve and the ones that it can't.
A pragmatist, Zoufaly advises that VB developers first accept the following immutable truths:
you should not attempt migration until after your migration team has studied and learned the .NET environment
migration, particularly the first time you do it, is going to be very frustrating
migration is in no way a hands-off process
some applications simply cannot be migrated automatically
the only applications worth migrating are those which the company intends to significantly enhance with functionality that only .NET can provide
In other words, if you've imagined a process by which one loads some VB6 code into the wizard, does a few days' worth of debugging and testing, and emerges with a VB.NET application, you are living a fantasy. And the sooner you abandon that fantasy the better off you will be.
Zoufaly advises that developers should expect to spend a minimum of two to three weeks in training on the migration process and using the migration tool in practice before attempting an actual migration. And that is two to three weeks on top of the weeks and months that developers should spend learning VB.NET and the .NET framework.
"I'm not sure that [VB6 developers] realize how much more difficult it is," says Zoufaly. "But they should be able to get it. The best advice I can give is to learn VS.NET first."
After a developer is sufficiently comfortable with .NET and has spent several weeks in studying the migration process with the tool, Zoufaly says that a migration should progress at an average rate of just 7,000 to 10,000 lines of code per week. Therefore, a 1 million-line VB6 application will take 100 weeks—two years—to upgrade. Seems a little slow for something that Microsoft had the hubris to dub a migration "wizard."