On migrating from VFP to .NET (Site: Les Pinter)

Link here

Excerpts:

However, back in March of 2007, Microsoft officially announced that they would no longer enhance FoxPro. This means, among other things, that it may not work with future operating system releases. It already conflicts with some Vista features. If you haven't installed Service Pack 2, don't. Enough said.

---

As tables grow, multiuser installations on Local Area Networks experience performance degradation. Logging users off to reindex files is a major struggle, and the fact that it has to be done pretty regularly is a real problem. And anyone who has access to the network share where your tables are located has the ability to copy the data or change it, bypassing your excellent efforts to keep the raw data clean.

---

In addition, it's increasingly difficult to find skilled FoxPro developers. Some are retiring, and new ones are few and far between. I don't know of a single university that teaches FoxPro; most of them teach .NET languages. The handwriting is on the wall.

---

Rewriting an application sounds daunting, but in the case of a rewrite, you've already done 70% of the work; the systems analysis that defined your business rules.

---

You never know what Microsoft's going to do in the future; but you can be ready for it.