From the blog:Where you want to go from here is really up to you. I can say, however, that the VFP team is working on the next version of VB.NET (as we’ve talked about for over a year now), and there are some interesting tools that help you either go to .NET, or integrate new .NET code with your VFP applications. There are also at least two .NET frameworks written by folks who come from VFP. There is also a good community on the Universal Thread made up of VFP people who have already added .NET to their repertoire. But again, it’s up to you.
From the comments:
I will spare myself the searching for reasons to keep it alive. The people paying the bills are opting for the mainstream and that is NOT VFP: period! If any one of you can continue to milk the goat, have fun and good luck.
More:
I feel like left alone out in the rain.
Reading this blog makes me feel even worse.
Mr. Griver has talked to 50 different companies?
Well maybe someone should have told him the world is bigger
and the VFP users consist of a lot more than 50 companies.
One of the good sides is, we are free to go where we want to.
Even Mr. Griver has approved this for us.
Anyone interested in trusting a company and in people behaving like
this?
As it's for me..... no way.
I did not expect MS giving the source code away.
It's just so obvious. We are all to stupid to understand the source and
the entire community has done nothing towards the development. MS has
always shipped a perfect version without any bugs.
I would feel so guilty by killing thousands of jobs.
Instead of acting like we got something to celebrate.
This is so disgusting.
More:
YAG why dont you quit talking to your friends that WONT sign the petition and talk to the "real" VFP community. You all should be disgraced by your actions.
Another:
I see a theme here you cant release the source because we "the VFP community" are not smart enough which echos some VP at MSFT [SOMA'S] comments that the vfp programmers are only upset because we dont want to learn a new language. I guess you are only a real programmer if you work at MSFT.
You guys just dont get it.
WE NEED A SUITABLE REPLACEMENT FOR VFP AND MIGRATION PATH AND THE TRUTH WHY MSFT DROPPED VFP!
More:
Another: