Reverse an MS decision LOL. About a VFP decision they made ROFL.

At this point I only hope that MS will fix the mess they apparently made with SP2 for VFP. After all THEY said that VFP would be supported until 2015.

VS2008 is better than VS2005. LINQ, C# 3.0. I like what I see but still for data manipulation it's not (like you said) VFP.

Here's what I wish for from MS:

1) VFP will really be supported until 2015
2) The next version of VS (Rosario) give it to us as easy as VFP when it comes to handling data
3) The next version of VS is released in 2012. That will give VFP developers enough time to make the move before support for VFP is stopped.

If MS cannot provide what I just enumerated

Perhaps Etecnologia (or similar projects) will be our only hope of extending VFP as a serious development environment and give us more time to transfer our apps to .net (pieces by pieces).


>I agree that VFP is still a better choice for some application. But you have to take into consideration that it will no longer be supported in 7 years from now and that resources will get more and more difficult to find.
>
>MS have decided to pull the plug on VFP and I can understand their decision. I don't think that we will have the power to reverse MS desicion, so why not put our energy in learning another tool? Like you said, the market isn't very favorable for VFP-only developer and my guess is that it will get worst in time. Demands for .NET and ASP.NET is however very high.
>
>>I understand what you mean Sylvain. I read everything you said in this thread. .Net is a very cool development environment but still for certain apps VFP still has its place. But given the fact that MS pulled the plug on VFP forces many developers to use the new cool things to make themselves employable in today's economy. VFP's still a very capable development environment but the jobs are tougher and tougher to find for it.
>>
>>So nowadays the game is called .net and C#