Rick,

According to the piece, it was a stand-alone system that they wanted to migrate to the web. That to me does not seem to be a "just because" reason.

Granted, there are some VFP DLL's still in place, but based on what I read, the vast majority of the app was replaced with .NET/SQL Server. From technical perspective, in the long run, the company is better positioned strategtically. Whether it is technology or staffing - they are better positioned for having gone down the .NET/SQL Server route.


>>IMHO, this will be the most damaging to VFP yet. It insinuates that VFP is dated technology and not a RAD tool in comparison to .net. Case studies like this could well be the demise of the best development tool available.
>
>Yeah, well this case study doesn't really mention a valid reason for them to having switched to .Net. The Web Services stuff most likely could have been done just as easily with VFP especially since it sounds they are in fact still using a VFP backend to actually get at their data.
>
>THe biggest farce here I think is the fact that they apparently did this for UI reasons. If there's one thing that is weak in .Net it's the UI (not that VFP's UI is that strong and less buggy).
>
>There are possibly good reasons to use .Net but a migration 'just because' is not really a good reason. It looks to me this case study points exactly at that though...
>
>+++ Rick ---
>
>>
>>
>>>http://www.microsoft.com/resources/casestudies/casestudy.asp?CaseStudyID=14755
>>>
>>>"CDS wanted to replace Visual FoxPro with a recognized and widely accepted platform."