Migrating Applications from Visual Basic 6
Introduction
The first thing that you need to ask is, "Do I need to move my application to .NET?" If the answer is "Yes," you have a lot of though choices to make, such as:
- Should I go for an application re-design?
(continued)
 |
Web Devs:
Moonlight as a Game Developer and Win Cool Prizes by Accepting the RIA Run Challenge
Now, your mission--should you choose to accept: Take your shot at gaming stardom if you think you might have what it takes to build a cool RIA game and you could win an Xbox 360 or other fabulous prizes. Hurry! You only have until May 15, 2008 to enter.
»
Article:
Leveraging Your Flash Development with Silverlight
You're not giving up Flash any time soon (and we don't blame you.) But if you could get your Flash application working in Silverlight, why wouldn't you? We show you the tools and techniques required to have your rockin' Flash application rolled for Silverlight. Learn more here.
»
Article:
What Does it Take to Build the Best RIA?
With the proliferation of Rich Interactive Application (RIA) platform choices out there, you no longer have to take a one-size-fits-all approach to developing your next RIA application. Knowing the strengths (and weaknesses) of each platform can help you to decide the best RIA for your next application.
»
|
 |
Should I just use the VB to VB.NET migration tool just so my code compiles and runs as managed code?
If you choose the latter, you have think on the lines of whether to write an automated tool to make this happen or to do a manual migration. I call it porting; it is not exactly migration.
- Should I convert the VB code to .NET first and then go for a re-design?
The Problem
You have decided to migrate Visual Basic applications to .NET and need to define a strategy for migrating Visual Basic applications to Microsoft C#.NET or VB.NET.
The Strategy
The strategy changes in each case based on the following scenarios.
Scenario 1: Application Redesign
- Remodel the application design from your existing VB 6.0 design.
- Analyze the existing design and identify areas for improvement based on the features provided by the .NET framework.
- Re-design component functionality based on Step 2.
- Perform a Proof Of Concept/Prototype build.
- Identify resources and prepare estimates.
- Further down with Construction, Testing, Parallel, runs, and so forth.
Scenario 2: Apples to Apples.NET Migration
- Evaluate the existing application.
- Perform a Proof Of Concept/Prototype build.
- Identify resources and prepare estimates.
- Use the standard VB to VB.NET migration tool.
- Make further code changes/modifications based on your customized requirements, ones that the migration tool cannot handle.
- Proceed with testing, parallel runs, and so on.
This scenario works well when you just have one application to migrate. If you have more than one application to migrate, you should start thinking about automating Steps 2 and 3 or, at the least, Step 3.
Instead of having your developers do all the changes manually, it might be worthwhile to write an automated migration tool that will take care of the following:
- Running the VB to VB.NET migration tool on your existing applications.
- Customizing the converted VB.NET code based on your requirements.
- Compiling and building the converted code.
- If your preferred language is C#, use the VB.NET to C# conversion tool and then recompile and build the new code.
Basically, automate code generation, modification, and compilation.
(Full Size Image)
Scenario 3: Combo.NET
I have seen some companies that want to follow this approach:
- Execute Scenario 2.
- Stabilize .NET application in production.
- Execute Scenario 1.
If you really want to make your existing VB applications powerful and your enterprise is moving towards service orientation, you might want to take a phased approach and then move to .NET. In this case, you will find this scenario more cost effective and the resulting applications will be more scalable and reusable.
Conclusion
There are a lot of strategies people talk about and all are pretty much based on the above-mentioned scenarios except the one that says "copy and paste your code into VS.NET IDE, iteratively compile and fix it until it works;" no, I wouldn't recommend that route.
It all depends on feasibility, so weigh your options, formulate, and finalize a strategy for your migration efforts.
About the Author
Yogi Abhyankar
Yogi Abhyankar is a Microsoft Certified Solutions Developer for .NET and is working with the Microsoft.NET platform for several years. He has a Bachelor's and Master's degree in Computer Science. Contact information
Email: emailyogi@gmail.com
All
IE 7
Firefox 2.0
