Listly by John Smith
Why is a question about VB6 to .NET migration so timely? Visual Basic was created by Microsoft in 1991. A lot of in-house applications were implemented along with an ecosystem of third-party components.
But later, Microsoft abandoned Visual Basic in favour of the modern .NET Framework. The final VB release was version 6 in 1998. According to Microsoft, Windows supports core VB6 functionality which is “used in the majority of application scenarios” under the so-called “It Just Works” commitment.
With Microsoft no longer supporting VB6 development, many companies consider transferring their old software to modern programming languages. The main goal is to improve software performance and security. New technologies and approaches, like VB to C# migration, keep businesses competitive and adaptable to market changes.
In this case study, we describe how we helped our customer rewrite slow AutoCAD functions and convert Visual Basic to C#. As a main result, we decrease the software license costs for 75% of our client’s users.
In it’s heyday, Visual Basic 6 was the enterprise application development language. Over time, VB6’s client-server architecture morphed into a .NET platform. However, many businesses continue to rely on legacy applications. Macrosoft’s VB6 migration practice transforms legacy applications into a modern .NET platform.
Even with the help of VB to .NET migration tools, it is critical to plan carefully in order to ensure success. This whitepaper presents eight recommendations that you should take into account when planning a code migration.
Follow John Browne on a brief history of Visual Basic and learn how to convert VB code to C# easily.
BASIC as a programming language dates back to 1964 when Dartmouth professors John Kemeny and Thomas Kurtz decided to create a very, well, “basic” programming language to teach students how to program. At the time, the existing languages were either extremely low-level or, like COBOL, too ugly to look at.
Why is a question about VB6 to .NET migration so timely? Visual Basic (VB) was created by Microsoft in 1991 and became very popular. A lot of in-house applications for enterprises were implemented along with an ecosystem of third-party components.
But later, Microsoft abandoned Visual Basic in favour of the modern .NET Framework. The final VB release was version 6 in 1998. Visual Basic 6.0 IDE is not supported anymore. According to Microsoft, Windows supports core VB6 functionality which is “used in the majority of application scenarios” under the so-called “It Just Works” commitment.
Why migrate from VB6 to .NET? The final VB version was released in 1998. In 2008, VB’s support was discontinued.
What does this mean for companies with internal applications built with Virtual Basic?
Today, companies still using Virtual Basic 6.0 IDE are forced to migrate internal applications because the programming language is no longer supported. A still available option to those companies is migration to the .NET framework.