Paul Vick the voice of reason.
Paul Vick chimes in with some well thought out reasons why migrating VB6 to Visual Studio.NET isn’t a good idea. My favorite quote:
“To?start with the second point first, to those who think we should?integrate VB6 into the current Visual Studio shell, I can only offer the perspective of a developer whoís worked in both codebases: best of luck. ”
His other points addressing the idea of creating a non-integrated version of VB make sense too and extend what I said in my first post. How much longer do the VB6ers want? They’ve had 5 years to migrate their code. The need to migrate isn’t something that just popped up. Should Microsoft spend 4 years integrating “VB.COM” into Visual Studio.NET or 2 years shipping an update to VB 6? If they do ship a stand-alone version, what new features should it include? Generics? Wouldn’t that just be giving the VB6ers a placebo? It doesn’t cure their problem.
Ad
.NET HTTP Abstractions group
|
| Subscribe to .NET HTTP Abstractions |
| Visit this group |
Tags
O’Reilly Blogger Review Program
Books I’ve worked on
Contributors
Links
Herding Code Podcast
- Herding Code 133: Derick Bailey on Backbone.js 2/3/2012
- Herding Code 132: Phil Haack, Keith Dahlby and Paul Betts on Git for Windows developers 1/20/2012
- Herding Code 131: Chris Williams and Matthew Podwysocki on the Javascript community 1/4/2012
- Herding Code 130: Dave Weaver on Loggr – a realtime analytics service built with MVC, MongoDB and SignalR 1/2/2012
- Herding Code 129: Rob Reynolds on Chocolatey and the Chuck Norris Frameworks 12/13/2011