This is an interesting question. If you look at the end result of a project, I would say there is very little you can do in .NET that cannot be done in VFP.

There are however, technolgies that can be consumed by .NET that cannot be consumed by VFP. Specifically, if you want to create web services without the extra COM layer, you cannot do that in VFP but you can do it in .NET. When you start seeing more and more .NET controls, VFP won't be able to use them. VFP cannot use ADO .NET directly either. Then again, there is COM/Interop that goes to addressing some of these issues.

On a more abstract level, I would say that .NET offers a level of support, commitment, and innovation on MS's part that VFP does not. From a human resource standpoint, it will be far easier to find .NET developers as opposed to VFP developers.

I would say there are more business implications than technical implications. And FWIW, the business implications are what normally do and should drive the decision...


>My employer asked me What does .NET offer that I can't do in VFP and I'm not sure what the answer is. Does anybody have an answer to this? I really want to get a good listing to talk with my boss.
>
>Thanks,
>
>Isabel