>AFAIK, they won't add any new functionality other than offering the possibility of running in .NET. They may add a couple of years to the life of VFP applications, but that won't prevent VFP from being obsolete.
>
>I'm still amazed to see developers so attached to a given tool that they won't even try to learn/use anything else. It's a little bit like a construction worker who is the master of the hammer. Everything look like a nail to him and he won't let go of his hammer for nothing. Sometime a screwdriver may be a better option to work with a screw.
>

When the company that makes the hammers decides to quit making them and tells you the that the 'new' way to drive nails is by holding your thumb over the nail head and pounding on it with your other hand, you might think fondly about the hammer.

Developing data driven applications in .NET (and especially ASP.NET) is a huge step backward in time.

.NET has a lot of bells and whistles, but the simple tasks of getting, binding, and manipulating data in VFP are stupidly complex in .NET.