By John Kullmann | Published on January 10th, 2023 | Last updated on October 29th, 2024 |
If you happen to be working for Microsoft at that time you would’ve been part of the excitement of Visual Basic 1.0 being released for the first time. Throughout the next eight years, a new version of Visual Basic Application was released every 1 to 2 years with the last version Visual Basic 6.0 released in the summer of 1998.
Visual Basic dramatically changed computer programming. It was modular, relatively easy to learn and was simple to use compared to other programming languages in the 1990s. It was derived from Basic and provided a Graphical User interface to access databases, objects, and controls.
Visual Basic 1.0-6.0 were so popular during the.com boom of the 1990s and early 2000s that applications were built for virtually all industries covering a wide array purposes and functions. Unfortunately, good things come to an end. All versions of visual basic from VB 1.0-6.0 were retired into 2008 by Microsoft. So, since that point they are no longer supported.
Visual Basic 6.0 has been out of support for 10 years now, yet many sophisticated mission critical applications continue to run on it, while supporting business operations. Why? Well, in the words of a client, “It is simple… they continue to work like a champ”.
For whatever reason, be it retirement of the development force, wanting to build out new functions & capabilities, or ensuring compliance with security audits; companies are facing the reality that they need to find a way to move beyond Visual Basic 6.0.
At Macrosoft, we have expert teams and proven methodologies designed to support a logical, phased migration from a working legacy application to a new modern technology architecture. We use a “like-to-like” modernization approach to allow complete parallel testing, followed by system and enhancements in a second phase of the project.
Navigate to our website or contact Macrosoft to learn more about the process used to keep your company running while modernizing your VB6 application or migrate Visual Basic to .NET platform.