Migration of a big project from vb6 to vb.net

Question

0.00/5 (No votes)

See more:

Hello everyone,

My company want to migrate a big project from vb6 to vb.net
I read some articles on the net, but i would ask to you if there is a way or a best practices to do it.

The vb6 project have a main MDI form with a lot of child forms
My idea is to do a progressive migration, adding just a form at a time. Could be possible?

I tried a massive migration from vb6 to vs2008 , but as i supposed , was interrupted.

The vb6 application have some wrong architectural choices made during the years: they used many global module, variants ,many third-parts controls.

If you had any experience about it, could you give me some suggestion?

Thanks.

Luke

Posted 15-Mar-12 23:19pm

JasonSky77

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Maciej Los · Answer 1 · 2012-03-17T09:28:00

The vb language is similar to vb.net but not the same. If you think, there is a simple way to make migration from vb to vb.net, a speccially, when you see many
"wrong architectural choices", you should know, it doesn't exists. Of course, you can find "translators", but in that way you are copying "wrong architectural choices".
Probably you'll need to write it again, planning classes and interfaces, removing third-parts controls.

Bernhard Hiller · Answer 2 · 2012-03-18T22:16:00

Solution 2

Since VB6 objects typically are COM objects, you could be able to use some of them in your new application.
But if there are to many "features" in the architecture, the only chances are writing the application completely new from scratch or stick with the old VB. Both options are bad.

Posted 18-Mar-12 22:16pm

Bernhard Hiller