Hi Ken,

>You will be able to create and run a VFP application on Longhorn, but it will be a 32-bit COM based application only and not use the new WinFX APIs, Indigo, the Windows Framework (.NET Framework), Avalon (XAML UI), etc. Now, you may not need those things for the VFP app you are creating and using. For more details, you're probably best off reading about the technical details online of these technologies announced at PDC last week.

After reading all messages in this thread (till now) I got really confused and think many others got too. Pardom me for being so naive, but believe that many developers like me are not so aware of all those new technologies that are present or those still to come. Many of us, I believe, don't have the time (our fault?) or the means (really not our fault!) to get updated to all that comes day after day. Bad to us who make our livings based on our work with VFP.

This is the beginning of the end of VFP? It can't follow the new trends and will be obsoleted like FoxPro DOS was?

What I would like you to, please, explain is what's going on with VFP regarding that future, and what will happen with VFP after all that new stuff comes. What will be the impact of all that when Longhorn comes (and that many new acompanying technologies) on regular developers that make regular applications.

As, very happily, JVP said, and I fully agree with him, not everything is built to run in the web and not all apps should consume web services! The way things are stated by now it seems THAT IS the way to go for ALL developers.

What is the target developer for VFP in the eyes of MS? Are they a *real* market to care about?

Regards,

Fernando