>>At least it'd be back again in the big (VS) box with the big boy's tools.
>
>And that's not a good thing IMHO. See my reply to Walter earlier on this.
>
>Do you really want to install VS.NET to install VFP like you had in VFP 6.0? If you want to install VFP 6 you have to go through a massive install to install VFP. It'd be much worse with VS.NET. Further while VFP was in VS 6.0 it didn't really help the popularity of the product at all. Sure people had it and could use but very few people did.
>
>In addition the VFP team would be back to be tied to the VS release schedules and having to deal with extra overhead for making sure the schedules are synched.
>
>I'm not sure that any of these are beneficial features..

I agree completely with you that it's not necessarily a good thing.

But to have some recognition in the industry I guess that the price to pay is'nt that big.

Even when VFP was in the box it did'nt have the recognition it should have received. So now that it's not in the box its recognition is not better <g>. No matter how good it is not being in the box is'nt the best marketing approach. At least being in the box would kinda force MS to explain why it's in there. Not in the box = Not an important development tool for MS.

I don't really mind having to install extra stuff. This process is only done once and that's it for a while usually.

Schedules? The way I see things right now it's not like there were 5 releases of VFP for one release of VS.Net. So synchronizing those with releases of .Net would'nt be something that bad.