Guest User

Microsoft won't "Bring back Classic Visual Basic"

a guest
Jun 4th, 2014
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.23 KB | None | 0 0
  2. Microsoft won't "Bring back Classic Visual Basic"
  3. Answer to community's proposal
  6. Status update: An idea you voted for has been closed!
  7. 1 vote has been returned to you Go spend your votes on more ideas...
  10. Bring back Classic Visual Basic, an improved version of VB6
  12. 7302 votes -> Declined
  14. We have read all of the comments on this thread and I’d like to
  15. thank you for providing your constructive feedback on this issue.
  16. Instead of merely repeating our support and migration guidance
  17. that has been laid out on, I’d like to
  18. address some of your specific comments here.
  20. To play back the feedback themes we’re hearing:
  22. - VB6 is awesome
  24. - VB6 needs to be brought forward and maintained: in a new release
  25. or OSS
  27. VB6 was and still is without a doubt awesome. VB6 made developers
  28. incredibly productive building a breadth of applications and as a
  29. result we have a wealth of applications and passionate developers
  30. to this day in 2014. One way I see our mission in developer tools
  31. is to empower developers to solve problems. This includes both
  32. today’s problems AND the problems of tomorrow. VB6, as you all
  33. have stated repeatedly in this thread, is an excellent tool for
  34. solving the problems of its day. We also stand behind our decision
  35. starting in 2002 to meet the current demands of our developers and
  36. the industry with .NET. For the scenarios VB6 set out to do, we
  37. see VB6 being “complete”. We feel good about VB6 being able to
  38. continue maintaining their applications for the past 15 years.
  39. Current needs ranging from distributed applications and services,
  40. to web applications and services, to devices, to new architectures
  41. and languages, required fundamental changes to the whole stack. We
  42. looked at how we could accommodate these needs through incremental
  43. changes to VB6 while maintaining its essence, and that was not
  44. possible.
  46. To address the modern needs we would need to go far beyond
  47. updating the language. We have to remember that VB6 is not just a
  48. language. VB6 is a language, a runtime, a platform library, a
  49. tool/IDE, and an ecosystem tightly packaged together in a way that
  50. made all of them work well together. We’ve worked with many
  51. customers on migration from VB6 to .NET and found that while yes,
  52. there are language changes, the dominating factor in migration
  53. difficulties isn’t the language differences. Even open sourcing
  54. the language/runtime wouldn’t solve the fact that VB6 was
  55. thought for a different set of problems, and the fact that its
  56. strength came from the end-to-end solution provided by all these
  57. five pieces working together. Take a change like 64bit, the
  58. complete runtime, tools and ecosystem chain would need to be
  59. retooled.
  61. So, moving forward what can we do? Where we have been able to help
  62. move forward is in our stance around support and interoperability.
  63. The VB6 runtime it is still a component of the Windows operating
  64. system and is a component shipped in Windows 8.1. It will be
  65. supported at least through 2024. This ensures your apps and
  66. components continue to run as you incrementally move forward to
  67. .NET. The support policy is here:
  68. There are
  69. numerous interop strategies that we developed and evolved to
  70. enable incremental migration as you upgrade your skills, described
  71. here:
  73. In summary, VB6 was awesome. We agree. We don’t expect or demand
  74. anyone to throw away their code or rewrite from any of our
  75. technologies unless it makes business sense for them to do so. We
  76. have to innovate to enable our customers to innovate. It is not a
  77. viable option to create a next version of VB6. We stand by our
  78. decision to make VB.NET and the .NET Framework. We think they are
  79. awesome too. It is not feasible to open source VB6 tools chain and
  80. ecosystem. The VB6 runtime was last shipped in Windows 8.1 and
  81. will be supported for the lifetime of Windows 8.1. Support and
  82. interop are great tools to move forward incrementally.
  84. I hope you feel we’ve listened to your feedback and that I’ve
  85. explained things well enough that you understand our decision.
  87. Paul Yuknewicz
  88. Group Program Manager
  89. Microsoft Visual Studio Cloud Tools
  90. Visual Studio team
  92. Visual Studio team
  93. Product Team, Microsoft
Add Comment
Please, Sign In to add comment