Sure. If Microsoft had its way every developer on the planet (Visual FoxPro or not) would be producing applications using and for only the Microsoft products with the largest return on investment. It's understandable. However, that doesn't mean that the Visual FoxPro Community has to go along with it - in fact I personally can't go along with it given that Visual Studio cannot be used solely to produce the kinds of applications that my customers want. I'm not saying no to switching wholly to Visual Studio out of some kind of blind love for Visual FoxPro... it's simply a business decision for me and my business is meeting my customer's needs. And given the adoption rates for C# and VB.NET, I'd say that many other software firms are making the very same decision. I'm not saying that Visual Studio is bad... in fact, it's one of the best IDE's I've ever had the pleasure of using and I love the C# language. It's simply that it is not a "best fit" for most of the applications I work on at my business.

The .NET framework is a big beautiful set of classes that can be leveraged from Visual FoxPro and I would encourage any VFP developer to find out what is offered there - Visual Studio and the .NET framework are NOT the same thing, so I was glad to see that you said "C# or VB" in your post. Some use .NET and Visual Studio interchangeably. Some ask the question like this... "Is Microsoft trying to get us to switch to .NET?". That's like saying, "Is Microsoft trying to get us to switch to COM?". That doesn't make any sense. We can use and leverage the .NET framework from Visual FoxPro where appropriate.

In the end, developers should choose the tool that best meets the needs of their customer. Whether that tool is a Microsoft product or not. For me and most of my customers that tool is Visual FoxPro and will continue to be Visual FoxPro for a long time to come. I work with a number of tools and in more languages and scripts than I can count on both hands, but when it comes to a creating a data-centric desktop application with blinding speed for the cost conscious consumer, Visual FoxPro invariably gets the nod at SweetPotato Software. And my customers are tickled pink.

>This is all beginning to look as if the VFP community will be gently moved to C# or VB over the next fifteen years or so. Any truth to that?
>
>>>The VFP Roadmap describes how VFP will be updated http://msdn.microsoft.com/vfoxpro/Roadmap/default.aspx.
>>
>>Regarding the Roadmap being the only determining factor in how and when Visual FoxPro will be updated...
>>
>>Re: Any Rumors on VFP10 ? Thread #1107872 Message #1109835