Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
FPD 2.6 to VFP or .Net
Message
 
To
28/06/2006 03:54:16
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
01132288
Message ID:
01132386
Views:
15
I have taken many Microsoft Official Courses as well as read many .NET books. My opinion is to use the books available from Murach:

http://www.murach.com/index.htm

This will get developers up to speed quickly and with little pain.

You should look into using a framework such as Mere Mortals or StrataFrame

http://www.oakleafsd.com/

http://www.strataframe.net/

The language you use is up to you. Being familiar with VB.NET and C# is not a bad concept. My experience is that VB.NET would let me do things like keep connections open, which our SQL Server and Oracle Database Administrators frown upon. Using C# if code to close a connection was not present then you would get an error and the Debugger would point you to the problem.

VB.NET is similar to VFP in many respects, but my preference is C#. It does not take long to be proficient in either language. Most Dot.NET software developers seem to be using C#. Use what you are most comfortable with.

Tom




>Dear Members,
>
>I have been following another thread about migrating from VFP to .Net. But, in my case I want your inputs about migrating from FPD 2.6 to VFP or .Net
>
>Our's is a general purpose Accouting software with about 400 users ( copies ). We are not planning a major change to database structure. It's used by Small enterprises with max 15 users in multi-user mode ( Dbf backend ). We don't give the source code. Customer is not bothered about technology used ( VFP or .net )
>
>Our aim is give a good Windows interface & printing with good ROI ( Volume sales, less cost ).
>
>Advantages of using VFP
> Code re-use ( say 30 % - year-end/reports code )
> Reports - About 450, DOS reports that print to DM Printer
> Familiarity with Language
>
>Disavantages of using VFP
> Lack of trained developers
> Technology obselence ( assumption ) - Like 64 bit, Unicode support.
>
>Advantages of .Net
> Easy availilibity of trained developers
> Latest technology ( Perception of investors, developers )
>
>Disavantages of .Net
> Local cursor processing
> C# - Learing curve & time taken to relases the product ( 1st version )
>
>
>We are already behind market ( still a DOS version ). What would you suggest us to use. VFP or .Net or release a version in VFP & migrate fo .Net ( only if conversion tools are good enough )
>
>Regards
>
>Rakesh
Previous
Reply
Map
View

Click here to load this message in the networking platform