>So MS shouldn't be pushing it as Middle Tier quality? Is its functinality not accesible from the VS shell? I still don't understand why you want to "dumb down" the developer's suite, it only makes sense tomake itmore versitile, or s that too logical?
>

Ugh... It is not a matter of should. MS won't. Therefore, we could argue should vs. should not until the cows come home. A true excercise in futility..


>And most people that use VB probably dick around with it on the weekend. I'm betting the ratio of VFP developers that use more than 1 tool is eqaul to the VB developers tha>

VB developers have always had to use other tools. VFP is much more self-contained. Your average VB developer uses more tools because he has to. I don't really care since that is not relevant to my point.

My bet is that many, if not most VFP developers are going to stay in VFP - away from .Net for the simple reason that they don't build apps that are .Net related. The same can be said for many VB developers. I think a lot of folks are going to stay with VB 6 for quite some time to come. I think it is going to be 2-3 years before you see wholesale adoption of this new platform. Of course by then, MS will most likely inititate another phase shift..< s >..


>
So? THat makes the product (Visual Studio that is) more robust. But then, MS has its golden chains on you, so there's no use convincing you that there's another method to designing an application.
<

Yea, MS has it's golden chains on me....thats a laugh..!!

< JVP >