>>I'm not exactly kidding. At the MVP summit, the VB (classic, not .NET) MVP's were pretty darned disgruntled. We've been hearing for years that our tool is dieing. Theirs is frigging DEAD. <g>
>
>Absolutely. I shared my flight from Atlanta to Seattle with one of the last VB6 MVPs, and the guy felt more like a dinosaur like we never felt.
>

Yes. They're hopelessly abandoned.

>Anyway, having worst cases than ours is not something to rejoice.

Oh, definitely!

I actually predicted the demise of VB six years ago, but I thought the threat would come from VBA. Once VBA became available in all apps (which was at one time a goal), why have a standalone compiler? Somewhere along the way, the "grand plan" for VBA seems to have disappeared from all "roadmaps".

Did you notice all the questions from the Office/VBA MVP's about whether it would be continued? No matter how many times MSFT has said "we will continue this" they still ask.

Even the Access guys were nervous.

>But what I think here is that the complaint seems to let aside that Microsoft has supported FoxPro -even while it is clearly not a strategic product- for more than a decade, while .NET is still a brand new product, and some of its pieces are already in jeopardy -think Remoting, for example.
>
>Just my .02

Worth far more than .02, my friend!