>
>With the looks of things, even if it doesnt get folded into the common development shell, it seems to me the common tools like win forms and perhaps other web services will get us using the common development shell whether we like it or not, in order to create parts & pieces that we'll use from within VFP.

You're right. I will definately be using web forms, the COM debugging stuff, and other things from the VS shell. My point is that VFP will eventually be folded into the shell too, which is too bad.

>
>For large & complex enterprise apps I think it would be a big deal. For the sake of bragging rights (after all us fox folks are typically a territorial bunch for the most part right?< g >) I think it's also a big deal... but can I live without it initially? Sure... but all the more reason to get off the fox fence and start learning more than just basics with one of the varsity team tools.

Don't get me started on the varsity/jv crap that the VB weenie rolled out in the video. I'm pretty close to cancelling my vbpj subscription cause of what he said. Just because VFP isn't in the shell doesn't mean it can't play as well as the other tools. I'll be using other tools just as I do now.

>
>Think about this... we've been seeing glimpses of VFP7 for a quite a long time now. Why havent we gotten it yet? VS 7 was delayed. CLR is pretty massive change IMHO for all the other dev tools, no wonder they delayed it. Now look at how long it's taken us to even get a promise of VFP OLEDB provider. Are we really gonna keep the majority of out skilled set focused on a minor play tool thats constantly coming into the game late always guessing if we're going to get to play with the big boys? I dont know about you but it's starting to get old.

Keep in mind that the Fox team is a hell of a lot smaller than the others. Most of the heavy duty work is done by one guy. As for the OLEDB provider, when did we first start asking for it? One version ago? I don't think things are as bad as some people make them sound.

I'm not going to speculate on CLR. At this point we don't know if VFP will or will not be supported.

>
>Funny you should bring up inheritance... Not only is VB getting inheritance, it's getting it in a bigger and better way from the way I see it. Multiple language inheritance... that's awesome news! And here's the irony, we were shown VFP getting intellisense in a bigger & better way than VB. And now VB is getting inheritance in a bigger and better way. < g > figures.

Doesn't matter at this time if it's bigger or not. It's gonna take most VB developers a long time to figure out how to use it properly ... my guss is it will be one or two versions down the road... and (again, my opinion) most VB people won't ever figure it out.