>Sure, we can sell it, but it's an intangible benefit at best.

I agree with you re: it takes (much) more work to do the same thing in .NET for most anything data related. That is not necessarily the case for other non-data related tasks. I'll hand it to .NET when it comes to having built-in functionality (via classes) for *MUCH* more than VFP if you can figure out where it is (no easy task).

That doesn't mean I prefer developing in .NET for windows apps. Far from it. Reality has to step in though.

The real benefit to the customer and to the owner of the code with .NET is that in 5-10 years the .NET code will very likely be very viable on whatever the current version of Microsoft's desktop/server OS exists at the time, and because Microsoft has thrown billions of $$ into the technology, you can bet that .NET will still be a major development platform.

I really don't like the idea, but I will not recommend developing a new application for a client in VFP.