>Microsoft has been making a very big deal about .Net as the strategy for Microsoft. And how >they are creating a common language interface (CLI). Guess what, folks? Xbase is not a CLI >language. And VFP will not be part of the future of Visual Studio.
>This is the news release confirming the kiss-off: >http://msdn.microsoft.com/vfoxpro/prodinfo/vfp7.asp
Quote from this release:
"Shipping separately gives us not only the flexibility to ship Visual FoxPro 7.0 sooner, but also the ability to ship future versions with a shorter product cycle," said Wenger. "We don't have to wait for the next version of Visual Studio."
FoxPro is NOT dead, and you are hurting the careers of VFP programmers by spreading this false rumour. How would you like it if I spread rumours that products that you depended on for your livelihood were soon to be declared "dead"?
You also seem to be laboring under the misconception that there will never be a robust way to integrate VFP into a web-based solution. Since VFP will obviously continue on, someone will eventually develop a means to do this, if they haven't already.