>We have a 12 year old, very fat client Fox app with over 100 tables currently in VFP 9. We are hooking to a SQL backend over the next year or so, then re-writing the middle and UI in C#.
My Take--
If your VFP app was developed in 3 years time, you will add a minimum of 1 year+ to have a complete and full blown C# version (windows) even if you have a 3rd party middle tier code generator to access data - i.e. MM.Net and the like. It's a just a rough estimate though...
What's painful in VS development is that it's too slow in some areas like: project instantiation, compilation... It has a longer data manipulation code. Looking at the LINQ promises, my guesstimate is that it shortens your code to only 30% to 40% of the previous .Net data manipulation code length. Meaning, VFP Data manipulation is still simpler and faster to a certain extent. Others may disagree but that's my honest opinion and assessment...
But overall, moving to .NET is worth the investment - money, time, and effort...
>It is all driven by our clients' IT departments. They told us they would not accept Fox anymore so we had to start moving away.
JESS S. BANAGA
Project Leader - SDD division
...shifting from VFP to C#.Net
CHARISMA simply means: "Be more concerned about making others feel good about themselves than you are in making them feel good about you."