Hi,

I think it depends on the kind of project and your skill level - in VFP and C# or the alternative language. If you could accomplish the project using VFP within a relative small amount of time, it doesn't use 'the new technologies' (WCF, WPF, ...) and it's not obvious that it will use them in the near future then why don't use VFP for it?

I personally wouldn't use VFP for new applications any longer, just because of the strong typing, unit tests and all the other handy features that come together with VS and the .NET runtime and make your code more robust.

>I'm curoius - is anyone doing any serious, long-term new development with VFP?
>The last 4 companies I worked for are all moving to C#.net.