Hi, Metin.

>I couldn't move all of my programs from foxpro dos to VFP yet. I think so I won't need move another language at least five years more.
>
>I learned VFP before two years ago and it was hard me enough. I don't want learn another language. Enjoy with VFP!.. :)

I find it absolutely perfect. While I realize he importance of being able to interoperate with .NET and the importance of .NET as a platform, I still encourage people to stick to VFP in the scenarios where they don't really need to move, or where VFP is still a better solution.

For example, I'm helping a local ISV to rewrite their point-of-ale application from VFP to VFP. Actually, their current solution uses FPW 2.6, a lot of DOS-inherited code, etc, and I'm helping them move to a fully OOP model with a better architecture and more flexibility to enhance the product and maintain it (something that became a hell for them over time).

They have thousands of individual installations in shops around the country, many of them with old hardware, sending files trough modems after hours. VFP and DBFs are just great for them. Trying to do the same in .NET will bring them lots of deployment and distribution troubles, higher hardware and software requirements, etc.

So, while I really believe that the notion of VFP.NET doesn't make sense, I still see a great value in VFP as-is.

Best regards,