Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

What is a good strategy for upgrading my legacy Visual Basic code?

April 26, 2017code good legacy strategy upgrading visual basic

0

10 Posted

What is a good strategy for upgrading my legacy Visual Basic code?

1 Answer

0

10 Posted

There are a number of possible approaches and the correct answer will depend on your situation. Generally it’s best to approach the process incrementally. One potential path is to use .NET only for new projects. Another angle is to upgrade legacy components that should be reusable in newer .NET projects. Another strategy would be to leave legacy COM components and ActiveX controls behind. These components can be accessed through .NET’s COM interop features. The correct strategy is a complex decision that should be considered carefully. Once you have chosen which legacy projects should be upgraded, the Visual Basic .NET Upgrade Wizard can provide a good first pass at translating your code to .NET. Generally, the output from this tool will be a close, but not perfect, transfer of your code to .NET. Specific areas of your code will probably need to be adjusted by hand to accommodate the changes in Visual Basic .NET.