It might be pointed out that, in the article, they are using vfp mtdlls and .NET interop to leverage existing code:
CDS was able to preserve some existing application logic, according to Robinson: “We have a set of Visual FoxPro COM DLLs, which we are using in our .NET application via COM Interop.”
Of course, this is way down at the bottom...
>>
>Probably already mentioned here, but I didn't see it. There's a new case study in the latest MSDN flash that refers to FoxPro: http://www.microsoft.com/resources/casestudies/casestudy.asp?CaseStudyID=14755
>>
>
>Interesting... A case study that highlights migrating from VFP to .NET...
>
>This statement jumped out right away:
>
>CDS wanted to replace Visual FoxPro with a recognized and widely accepted platform.
>
>The conclusion? MS endorses the notion that VFP is not an acceptable platform and that customers would be well served - in the long-run - to migrate.
>
>This statement was also interesting:
>
>The solution: convert AM4 into a Web service, using Microsoft Visual Studio® .NET and the .NET Framework. CDS Chief Architect Bill Sanders, said of the Microsoft .NET-connected solution: "We are amazed at how much a single developer can achieve in a short time using the .NET Framework. It's a truly incredible toolset."
>
>This one is very interesting because it goes directly to what some in the VFP community knock .NET for. Granted - case studies can paint a rosey - overly optimistic picture at times - but that is not the point. The point is that MS indeed does hear and listen to the critiques coming from the VFP community re: .NET. You now see how MS will respond...