Tool(s) are strangers to the real value of a software.

What makes the real value of software are the dev's ability to understand users' needs, build a consistent structure over data and corresponding classes, and implement consistent coding and documentation standards that allow instant software maintenance/evolution.

The more familiar you are with your dev. env., the easier for you to release high class software.

If you're a VFP expert, it'll take you years before you can deliver the same quality on another platform.

Though 10 years older than .Net, VFP is incredibly stable, even in high load scenarios like Web servers. If VFP was unstable or could limit your ability to develop a high class software, you'd legitimately dump it. Fortunately it's the exact contrary.

So, finally,
- if your client/users can wait 2 years to have a high class software and you no longer believe in VFP future for your carrier, go ahead on .Net
- if not, stick with VFP

PS: FWIW, using FoxInCloud, you can deliver a desktop and web application with the same VFP code.


>i am insteresting in what you say and what are your point of view about that ?
>what do you think about all the things we can download for VFP in codeplex ?
>thank you in advance for your answer