Microsoft Still Not Bending on 'Classic' VB Support
|
An online Web chat on Friday that was billed as a venue for Visual Studio 2005 questions evolved into a forum for the Visual Basic 6 faithful to bang the drum for Microsoft to extend support for the platform.
"Do you realize that our concern over the 'end of mainstream support' is not about two free phone calls, but rather the ability of VB6 applications to continue to run on future platforms, and of your commitment to fix any problems that might arise?" West asked Microsoft officials participating in the chat. Eric Rudder, senior vice president in charge of Microsoft's server and tools division, told chat participants that Microsoft's stance is not about to change. "This clearly is an important issue and deals with an issue that we have been working on for a long time," Rudder said. He continued: "I have heard basically two types of feedback. The first centers mainly around support and the second focuses on some sort of new VB6-based product. Let me deal with support first. Support is NOT ending. "Support is, however, transitioning, consistent with the roadmap that we disclosed in 2002. We are moving to extended support and that means we are entering a paid support period," Rudder said. Another chat participant asked "if the VB6 runtime is to be supported in Longhorn, and hence till approximately 2012, why not then give developers new tools to work with VB6, and hence build the bridge from both sides of the divide?" Rudder's response: "We will work very hard to make sure that support goes well. We have heard strong feedback about making sure that critical security fixes continue to be made. We will do this. We have heard a large number of folks ask for VB6 runtime support on Longhorn. We will do this. "We will also continue to monitor how this situation is working and make sure it works as smoothly as possible," Rudder said. Next Page: VB6: But What About the Long Term?
"I know this disappoints many folks, but I think it's important to set expectations correctly. We want to do a great job on security. We want to do a great job on productivity. We want to continue to innovate in key areas like Data Access. For these areas, we are betting on VB.NET. "We are always looking for ways to make the transition from VB6 to VB.NET better. I think Whidbey helps a lot in this respect and I hope we can work together to do even more in future VS releases," Rudder told chat participants. West, like some of the other classic VB backers, wondered aloud why Microsoft is continuing to support FoxPro, another of its older dev tools, but not VB6. Rudder and other Microsoft representatives on the chat did not answer that question. After the initial round of VB-related questions and answers, Microsoft representatives and some of the other participants turned the discussion away from VB-related issues for the remaining part of the hour-long chat. But Microsoft's public positioning doesn't mean individuals in the classic VB camp are giving up. One MVP who signed the online petition noted that the issues raised by the VB6 backers are complex and far-reaching. "As I see it, they (Microsoft) are between Iraq and a hard place (so to speak)," said William Vaughn, president and founder of Beta V Corp. "On the one hand they want to get away from COM-based DLL-hell-ridden application architectures but they have created a whole world of developers that use Visual Basic 6.0 to create them. On the other hand, they have a cure for the issues raised by COM-based architectures: the .NET Framework. The problem is they can't seem to find a good formula to get existing Visual Basic 6.0 "'developers' to migrate, despite the stories of miracle cures." Vaughn said he was encouraged by Rudder's commitment to making sure VB6 will work in XP, Longhorn and beyond, as well as Microsoft's promise that it will continue to work on VB6 bug fixes and compatibility issues as new platforms evolve. But Vaughn also noted that "Microsoft needs to take a hard look at the disruption they've caused in the industry as they constantly churn the technology. "They can't expect to reinvent the wheel every five years or so and expect the world to adopt the new technology just because it's new and improved," Vaughn said. |
Create, Communicate, Collaborate with IT Professionals at Ziff Davis Enterprise IT Link.


Comments (2)
Hello
so right now whats the future of VB6 developer as i have been programming in VB6 for last 6 years
Thanks
Jawad Haider
ERSoft
Posted by jawad Haider | May 7, 2008 8:06 AM
What steps i need to take for my future working in VB6
Posted by Jawad Haider | May 7, 2008 8:07 AM