Microsoft remains "firm" in its plans to end free support for Visual Basic 6 at the end of the month, S. "" Somasegar, the corporate vice president of Microsoft's tools division, told CNET News.com.
corporate vice president
of Microsoft's tools division
That decision to end free support for Visual Basic 6, which was introduced in 1998, has causedamong some of Microsoft's developer customers, even those with close affiliations with the software giant.
Somasegar said that Microsoft's intention is to ease the migration of customers to Visual Basic.Net, the current version of the product, which is is designed to quickly build Windows desktop applications that tap into databases.
To do that, the company will introduce enhancements in the forthcoming edition of its Visual Basic 2005 meant to "bring back" some ease-of-use features that appeal to Visual Basic developers, he said. For example, a popular feature called "edit and continue" will make its way into Visual Basic 2005, which is due around the middle of the year.
Also, by the end of the month, Microsoft plans to open the VB6 Upgrade Center, an area on its Microsoft Developer Network Web site, which will have technical information to help customers learn Visual Basic.Net.
Microsoft is using a carrot and a stick to get Visual Basic 6 developers to migrate: it will cut off mainstream support for the product but the forthcoming version will add features in the forthcoming that recall VB6.
Despite protests from its customers, Microsoft is tied to decisions it made many years ago to move the millions of VB developers to its .Net development system.
"It's sort of like, 'Should I give you fish for dinner or teach you how to fish?'' Somasegar said. "We had this revelation 18 or 24 months ago, that maybe we should be expending our energies and efforts to make it easy to migrate (customers') skills to take advantage of the new world."
A break with the past Despite Microsoft's stated aim to help its VB6 developers move to the .Net version of the tool, many developers said the company has not done enough.
On March 8, disgruntled users of Visual Basic 6, or "Classic VB," published a petition complaining about the planned end of free support.
Spearheaded by close Microsoft partners, called Most Valued Professionals (MVPs), the group urges Microsoft to continue the development of the older version of Visual Basic and help customers preserve their investment in existing applications. It called on Microsoft to make VB6 one of the languages in Visual Studio.Net, the company's flagship development tool.
The transition to Visual Basic.Net from VB6 is not as straightforward as most Microsoft product upgrades. When it introduced Visual Basic.Net in 2001, as part of the company's Visual Studio family of tools, Microsoft made.
Decided in the late 1990s, those changes--meant to make Visual Basic applications more industrial-strength--were in reaction to the rising popularity of Java, noted Greg DeMichillie, an analyst at Directions on Microsoft. It is estimated that there are about.
"Microsoft was seriously concerned about Java or Web development taking all those VB guys away," DeMichillie said. "Pure compatibility with Visual Basic 6 was not a key goal."
Because of the shift in the underlying language, migrating code written in older versions of Visual Basic is more difficult than a typical upgrade. Also, learning Visual Basic.Net is significant jump for developers because it represents a completely different language than VB6, critics say.
Surveys by Evans Data indicate that the number of VB6 developers outnumber the people who have learned VB.Net. Forty-four percent of