In order to convert an application, there needs to be a sound business case. As others have mentioned, converting just for the sake of having a newer platform is not a legitimate reason; that reason often can be translated as 'developer trying to bill and create revenue.' Even if it is not that kind of situation, there is no excuse for an IT person to advocate moving a software application to a new platform for the sake of the platform. It is NEVER acceptable to rewrite an application solely for the sake of a new platform. The reason it is never acceptable is it is not possible to present a business case for such a conversion. (the most offensive example is a developer who wants to move to a new platform because they have skills in that particular platform as opposed to other platforms)

Now for an actual business case for conversion, there would have to be a cost-benefit. First there would have to be a tangible goal or result(s) that would be accomplished by leaving platform A and recreating the application on platform B. Both leaving the current platform and the move to the new platform must be considered and must meet the business case. A conversion is by nature expensive and requires time, money, and effort. It affects typically many users. So one must ask - for spending this much money and expending this much effort and disrupting this many users, what is the exact detailed benefit? And then, is that benefit worth the cost?

A business case by nature considers the only people whose needs matter - the end users/company/client.

So a business case requires one to be able to clearly state:
a) the concrete end-user benefits of leaving platform A
b) the concrete end-user benefits of selecting platform B as a new platform
c) a comparison of possible platform B's and each of their concrete benefits to the end-user
d) the concrete end-user benefits of the new converted application as compared to the old application
e) the costs involved, including money, time, and disruption of moving to one of the potential platform B's.
f) whether the costs in e) are worth the benefits

I have seen many potential conversion situations and have been responsible for analyzing and/or reviewing them. And I have yet to see an example of converting VFP to .Net that even comes close to meeting the business case requirements. Whether it is internal IT people or external consultants advocating a change, it is irresponsible -- and often immoral -- to implement a conversion that cannot be justified via a business case.

I grant there may be somewhere out there a justifiable switch from a VFP app to .Net, but I have never seen one.






>>Just out of curiosity - why? It rarely makes sense to convert a VFP application to .Net.
>>
>
>Why do you say that?