One of the main reasons VB6 developers didn't move to VB.Net was lack of backwards compatibility.
This lack of compatibility meant you had to continue to support legacy apps. There was no business case for rewriting them, just to have the identical application in a different language.
And if they did move from VB6, what VB6 developer would choose a Microsoft language knowing Microsoft had just abandoned them and would be likely to do so again ?
And if you developed for Office you would still need to use VB6's twin sister VBA.
As many VB6 developers said at the time, Microsoft were right to develop C#/.Net, but they made a mistake in abandoning backwards compatibility in VB.Net. A compatible VB7 would have retained VB6 developers, instead Microsoft lost the majority of these forever.
Sadly, Microsoft didn't learn the backwards compatibility lesson. Windows Phone 7 was quite promising. Then Microsoft launched the incompatible Windows Phone 8 and lost the mobile phone market forever.
Now that C# is rapidly losing popularity and VBdotNet is being abandoned it looks like VB6 users were right all along.
The replacement of VB6 with VB .NET lost many of its RAD aspects simply because it had to be hard line object oriented. That's why VB.Net never achieved the success of VB6.
I support VB6 programming, VBA programming and VBScript programming
No comments:
Post a Comment