Given the unpredictable nature of today’s market climate, many software-oriented companies are scrambling to cut costs and streamline their application development processes. For organizations utilizing Microsoft Visual Basic 6.0 as their primary development environment, the difficulty of achieving this agility was magnified by the April 8, 2008, termination of all support for VB6. Some resource-heavier organizations have the in-house domain expertise required to manage a migration from VB6 to the newer Visual Basic.Net; others face a tough decision.
Loading ...
Planning a Migration Route From Visual Basic 6 to .Net
Posted by: Michael Lock May 7, 2009 04:00 AMGiven the unpredictable nature of today’s market climate, many software-oriented companies are scrambling to cut costs and streamline their application development processes. For organizations utilizing Microsoft Visual Basic 6.0 as their primary development environment, the difficulty of achieving this agility was magnified by the April 8, 2008, termination of all support for VB6. Some resource-heavier organizations have the in-house domain expertise required to manage a migration from VB6 to the newer Visual Basic.Net; others face a tough decision.