This tag is for questions about migrating existing applications, or legacy code, from Visual Basic 6 to a more modern platform. Unfortunately migration is usually a tricky task. The most common target platforms are VB.NET and C#.
Here are some typical motives for migration
- To use a more modern programming language for enhancements.
- This will give some increase in productivity.
- This also keeps the developers happy, which is a valid business benefit in itself. There are bigger gains in productivity from attracting and retaining good developers than anything else.
- To use a fully supported programming stack.
- Although the VB6 runtime is still fully supported by Microsoft as part of Windows, many people worry that support will be dropped one day. The VB6 IDE is no longer supported.
Frequently asked questions
- What is the best strategy for migration? There are a range of different opinions, as can be seen from the questions tagged
vb-migration
! For what it's worth, here is a Microsoft UK page with their advice. - Should we select VB.NET or C# when upgrading our legacy applications?
- Risks around relying on Visual Basic 6.0 applications
- When will it be impossible to support Visual Basic 6.0 applications?