What if MS really liked VFP and that VFP is not the reason it's not a part of the .Net plans yet?
What if it was because of the community?
It's been said that VFP developers are older (average) than the other developers.
I don't know about other (younger developers) but one thing we can notice here is that the community is not really holding on when it comes time to be critical of something concerning their favorite product.
So could it be that MS would have liked to take VFP into the .Net bandwagon but held back when thinking that they would've opened the doors to a bunch of old whiners.
So to get rid of those that never seems to be satisfied about anything. Wether the big efforts put into marketing, The content of the documentation and so on they decided to let VFP aside of the most amazing product since sliced bread.
Ins'nt that food for thought?
*******************************************************
Save a tree, eat a beaver.
Denis Chassé