Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Task to Outline Rewrite of Major App to C#
Message
From
17/03/2006 11:08:54
 
 
To
17/03/2006 10:39:33
General information
Forum:
Visual FoxPro
Category:
Visual FoxPro and .NET
Environment versions
Visual FoxPro:
VFP 9
OS:
Windows XP SP2
Network:
Windows 2003 Server
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01105311
Message ID:
01105325
Views:
19
The "why" is the most difficult. Is there a demand for thin client? If so, it sounds like you'll have to do some major rewriting anyway.

I would look at using Windows Communication Foundation and Windows Presentation Foundation and doing it all in C#. That will give you the most longevity and provide the best options for enhancements down the road.


>I have been tasked to create a white paper for inhouse use to look at the business considerations in rewriting a major application (took 10 years to develop completely and is now in VFP9 but still has data handling code throughout accessing tables directly - no ntier development but many classes and new features have been added overtime) from VFP to C# using SQL Server 2005 as a backend. WOW.
>
>I have six weeks to complete it. A lot to consider and right now I am looking at the below options to include:
>
>Front End VFP, Middle Tier VFP, Backend SQL Server 2005
>Front End C#, Middle Tier VFP, Backend SQL Server 2005
>Front End C#, Middle Tier C#, Backend SQL Server 2005
>
>
>Right now there is no TRUE middle tier but if it is rewritten then it should be done with one to allow for the greatest options down the road for future modifications.
>
>using C# it would include options of winforms or webforms
>
>If we do this, then the company will invest in formal C# training (wow, what a terrific opportunity). Right now I only have my experience learning on my own at home).
>
>I know the benefits of using VFP data handling but there are many business cases for creating a separate dotnet frontend and even using data handling in net (yuck but it must be seriously considered). I do not have to present that information other than to list the pros and cons but will focus on the benefits and drawbacks (as a business, as developers, and from the customers perspective - sales) of each option listed above and the estimated manhours to complete each one. The original app may still exist if the rewritten one is strictly thin client. That will be determined as well. We have over a thousand customers so the need for thin and thick clients exist.
>
>Please do not respond with "WHY even consider this?" The task was assigned and I will do my best to complete it honestly and in a professional manner listing all aspects.
>
>Previous documentation and experience anyone is willing to share would be GREATLY appreciated.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform