There is a difference between creating entirely new applications or maintaining existing one. New applications are rarely created in VFP anymore. Most happen when the client isn't more specific than "must run on Windows XP" and the developer is a VFP developer who is quicker at creating the app in VFP than in .NET (or whatever). If I'm asked to develop a new application I usually propose .NET and then use .NET, or VFP, or whatever the client wants me to use.

For existing applications it's much easier. If the application is written in VFP this is a huge investment that you cannot easily throw away for the sake of using a different technology. Most clients quickly understand this point when you express it in hard currency and time to market. For existing VFP applications my suggestion is usually to keep it in VFP and extend in .NET. New features that can be written in .NET, should be written in .NET, but it's nonsense to migrate for the sake of migration. My clients take different steps right now. Some are doing their third attempt of creating a new application, this time in .NET. Others keep using VFP and just extending with .NET. Others are using VFP only. Others are only doing .NET. Some are abandoning Microsoft and switch to Linux and open source.

It often depends on the scope of the software. With application that are designed for a single client it's often no problem using VFP. The environment is under control of the company making it easier to accommodate for the application. For vertical market applications I definitely see a switch away from VFP now. .NET compatible computers do have the critical mass to make deployment possible without running into lots of issues. During the first five years this was a major issue not to go to .NET.