Greatest Hits ...
In all fairness, I have to admit that the "Greatest Hits" section of VBRun does make it easier to find the VB 6 support that Microsoft still has in one place. If you're still using VB 6, "Greatest Hits" is definitely worth checking out. There's nothing here that wasn't already in MSDN, but it's organized for easy access.
VB Fusion ...
The idea of using the vast new library of .NET software with VB 6 can make sense in the right circumstances. If you're committed to VB 6 but it still doesn't do everything you need, then the vastly upgraded .NET software probably does. VB Fusion is a marketing term that includes all the ways that you can actually incorporate this VB.NET software into your VB 6 application.
Rather than ask why Microsoft didn't just upgrade VB 6 directly with even some of this new functionality, let's talk about the VB Fusion idea instead.
First, this isn't a new idea. To see how this has worked out with another pair of languages: C and C++, you might want to read Eric Johnson's software essay, "C++ - The Forgotten Trojan Horse" (soon to be published as part of Joel Spolsky's forthcoming new book, "Best Software Essays of 2004"). C++ became a big hit largely by "embracing and extending" the efforts of the legions of C programmers. It's a proven strategy and it will probably work here too.
The more important point, however, is that it's probably going to be a lot easier to just bite the bullet and take advantage of all the new .NET functions using .NET. To use this stuff in VB 6 may be possible, but it sure isn't straightforward and easy. In fact, it might be that this is exactly what Microsoft wants you to decide.
I highly recommend the "whitepapers" written by Scott Swigart, however.
- Using .NET from VB 6
- Can I Interest You in 5000 Classes?
- Using SQL Express from VB 6
If you read these articles and work the programming examples, you'll not only start to appreciate more of what .NET is all about, you'll also understand VB 6 better too!
Stay the Path ...
Of the three sections of the new VBRun site, this one is the least useful. Quite honestly, I don't know how they decided on this name because it's all about convincing you to abandon the VB 6 path and get on the VB.NET path. This might be an insightful view into Microsoft's fear that you might abandon Microsoft's path and that's the one they really want you to stick with.
Rather than providing any support for VB 6, the only information here explains VB.NET instead. Granted, it's carefully selected to appeal to VB 6 programmers, but it's still just VB.NET support. Hey Jay! I thought this was a VB 6 support site?
I admit it. This review of Microsoft's VBRun site is a little harsh and critical. But I continue to think that Microsoft is still not "getting it" and they need a little harsh and critical commentary to help them. Here's my "official position" again.
1 - I LOVE VB.NET! I can't imagine why anyone would consider using VB 6 if they're not forced into it by some external requirement.
2 - But when a company achieves the size and influence of Microsoft, they take on a public responsibility to their community and that includes issues like supporting people who bought into their vision. I think they owe some support to the people who still depend on VB 6 for their programming solutions.
And just to hammer the point home once more, it might help to review the latest About Visual Basic poll results for the question: "Are you planning to upgrade to VB.NET?" (Vote in the poll yourself!)
A significant number of votes have been registered - over 2000 - and the results now indicate a sea change in favor of a pretty ominous choice. Well over half of the people who have responded now say that rather than upgrading to VB.NET, they just plan to move to another language.
Pretty serious stuff, Microsoft!
