>>How is it any different than any other 3rd party tool for dotnet like Infragistics or Telerik or the frameworks which have to release a new version for every new version of .net?
>>
>>Once they get a product out there ready for production and if they make some sales they may be able to invest more time and resources into it in order to make it a renewable product.
>
>MS with its immense resources didn't maintain vfp as a viable language due to sagging sales. What makes you think that a small company will have the resources to bring this to market professionally with a handful of sbuscribers. they'll need 10's of thousands to buy into it which probably won't happen. Hell, there are people who argue about the viability of vfp vs .net who are still using vfp 6 and 7.

Be prepared to be surprised, very surprised.

Even if MS stopped all form of effective marketing for the fox many many years ago there are still many die-hard developers that use it as their main development environment. Heck there are even new cool tools being developer for it, for example the very impressive FoxCharts.

That is many stubborn VFP developers, and developers using other tools, that are not satisfied with everything surrounding .net as it is right now. Developers that don't see the urgency to dump VFP at this very moment because Fox is still doing everything they need to do.

Data-centric language. What an interesting concept. What are the .net languages oriented around that concept? None that I know of. So now there's a real development being made and the end-result will be a new language that will be data-centric. And it wont be a matter of a confrontation with the other .net languages. It'll be an additional language in the .net sandbox.

I may be wrong but your replies make me think that you are threatened by that new development. Please just try not to insult me in your reply ;-) I guess that there's still place for a civilized debate in that thread.

As a developer I've always looked for the tool that would make me the most productive. A mixture of C# and VFP.net would be so cool.

And... there are still tons of xbase (data-centric) applications running here and there. Many apps that were not ported to .net. If it ain't broken don't fix it. The fix in those cases would have been complete rewrites to vb.net or even C#. Many waited to see the evolution of ,net. What is the development language that MS pushes more and more these days? C#. I guess that the hard-core VB developers are not really happy about that one.

So I guess that many saw .net coming along but decided to wait and see a bit more to see what would happen. We all know how successfull VS 6.0 has been. Developers felt very comfortable with it with but then BANG! vs.net. A totaly different beast. First version. Many places thought hmmm let's see where MS is going with this. Then VS 2003, 2005, 2008 and 2010 is just coming fast.

So for those not seeing the urgency to flush their old development tool I'm sure that many are thinking. "Ok now with each release they get it always takes less and less coding to do than the previous version. Let's just wait a bit more to see because we can still live with our apps". So many developers waited and waited and waited and now VFP.net is coming along.

I'm sure there will be many die-hard developers that will be more than pleased to share the good news with the rest of the .net community. Showing them what can be done with VFP.net

But then again I could be totaly insane. We'll just have to wait and see.