Skip to main content

Why Microsoft Replaced Visual Basic 6.0 with .NET


Visual Basic 6.0 was released in 1998, it gained huge popularity and became one of the best products of the time. However within the next few years, rather than an updated version, Microsoft announced a new product, .NET which was a totally new environment where there is no backward compatibility with previous VB applications. .NET hit the market in 2002 with VB.NET replacing VB 6.0


 Introducing a new language is a significant risk, both from technical and marketting points of view. But Microsoft risked a new system without continuing their proven success at the time. Why?



What VB Actually Was

Classic VB had a few issues(read here) and it seems like Visual Basic 6.0 was at the highest position where Microsoft could deal these issues the easy way.

Unlike most other languages, VB applications depended on an essential hybrid environment, Win API + COM objects. This was the core reason for most of the issues. But from the times beginning, VB was intended to behave in this way. After version 6.0, MS decided to do away with this experiment and introduce a more formally designed platform- the .NET framework and thereby providing a new, more featured API interface for programs to deal with.




Different Approach

Microsoft could have used a different approach. Instead of establishing a totally new API, they could have tuned the VB6.0 compilers to produce better executables with decreased dependency. If they had done so, VB would have become a more powerful, optimal programming language while allowing super easy application development.
The main competitor, Borland came up with their own version called 'Delphi'. In contrast, though Delphi apps could make use of COM objects, most of the time they directly utilized the Windows API. Therefore, Delphi was technically ahead of MS VB.

New API

However, it seems as if Microsoft wanted to create a new platform. The .NET framework obviously ease up tasks while getting more control over the apps. On a side note, it must be noted that competitors of Microsoft such as Borland will face some tough time adopting the brand new market where MS will be playing by its own rules.




By design, VB was destined to be a given up language. In an overview, VB was more of an experiment for increasing simplicity at the cost of dependency. .NET emerged the successor. It adopted the dependecies in a more optimized way in a man-in-the-middle design. It targets easing and simplifying coding while performance is not a significant concern.

Comments

Post a Comment

Popular posts from this blog

Why Canned Salmon Got Soft Bones

Canned Salmon is a nutritious food, especially for protein and calcium. You can eat it right out of the tin. The fish bones are very soft and tender that they can hardly be noticed. It is a good source of easily digested and absorbed Calcium. But what made them so soft? Is it really safe to eat? because fresh Salmon bones look nothing like it!

Making and Extracting CAB files in Windows

Cabinet files(a.k.a. Diamond files) are the Microsoft Windows Archives. These archives can store multiple files/folders into a single file with or without involving data compression. Since every Windows system is natively compatible with cab files, Windows provide enough facilities to create, extract, or rebuild cab files without requiring additional software.

Why Atmosphere is Thicker at Equator

Atmosphere is the layer of gases that surrounds the Earth retained by Earth's gravity. Have you ever come across the question; what is the shape of the atmosphere? It's fair to think that the atmosphere is shaped somewhat like the Earth itself. because of gravity. We know that the Earth is not a perfect sphere. So, We can assume atmosphere to have a similar shape. But amazingly, the shape of the Atmosphere is affected by a lot of factors and the deformation is even more. Lets see why that is..