Stress Points in Converting Visual FoxPro to .NET

Stress Points in Converting Visual FoxPro to .NET

By Imran Salahuddin | July 14th, 2015 |

Hurdles while moving VFP to .NET

As far as an application developer is concerned, migrating Visual FoxPro(VFP) to .NET platform is the opening of a brand new world of possibilities.

One of the benefits of Converting VFP to .NET is that, .NET is not just a single language but a group of co-related development technologies that supports wide range of functionalities. Microsoft announced the end of life for VFP and come up with a top notch advanced .NET platform that allows developers to easily implement complex functionalities with a visually appealing user interface.

So, what are the critical aspects that are to be taken care of for .NET migration? Migration task needs to be handled with a clear plan of action. Below listed are some of the points that have to be taken in account, while performing a VFP to .NET migration effort.

Documentation

The first step in a migration effort is documenting the existing VFP application specifications. Prepare a chart of control architecture, variable declaration, and then commands. As set of Tables will be created with data and data types, define the relation between these data tables. The conversion directly depends on the size of the already existing application, such as the number of Forms/Reports, programs associated. By taking these values on account, the timespan of conversion can be determined. Business rules are to be taken into account as well.

Outline creation

For executing an application migration process, a detailed outline needs to be created. Add-on benefits that comes up with migration need to be considered in this phase. As VFP was built mainly to support desktop based applications, .NET brings the added benefit of leveraging the power of web.  Also, it should be noted that .NET scales well to larger sized applications. The best way to approach the migration process is to logically divide the application into different segments and concentrate on each section migration.

Data migration

Migrating the individual data files from VFP to SQL server or any other DBMS should be performed carefully. If the existing VFP application does have a SQL back end support, this process can be avoided. The immediate step is to optimize the existing data. Next step is making the program compatible to the SQL server or the migrated data base.

Stage wise Development

Application will be developed as different stages to ensure a smooth transition. Development phase is followed by testing and then corrections as required.  The migration effort ends with creation of applicable supporting documents such as user guides and manuals.
For more information related to .NET migration services, contact us.

Imran Salahuddin on Linkedin
Imran Salahuddin
Director, Migration Services at Macrosoft Inc
Imran serves as Macrosoft’s Migration Director. With two decades of industry experience, Imran continues to demonstrate his ability to ensure seamless migrations. Imran works with Project Managers, sales/strategy teams, and clients to ensure the successful migration of legacy applications. Moreover, Imran exhibits effective communication skills and an eye for quality service.

As a Microsoft Certified and PMI Project Management Professional, Imran can migrate a myriad of difficult technologies. Most recently, he migrated a VFP legacy application which communicated to networking equipment. Testing the application without detailed knowledge of the domain was the real challenge.

Imran also dedicates his time to IoT (Internet of Things), as well as Online Sales, and looks to improve upon all of Macrosoft’s existing verticals.
Recent Blogs

How to get The Most out of ASP.NET for Web Development
How to get The Most out of ASP.NET for Web Development
Read Blog
Microsoft .NET – A Popular Platform for Legacy Migration
Microsoft .NET – A Popular Platform for Legacy Migration
Read Blog
Business Impact and Risks associated with Microsoft Visual FoxPro
Business Impact and Risks associated with Microsoft Visual FoxPro
Read Blog
Migrate Visual FoxPro to .NET
Migrate Visual FoxPro to .NET
Read Blog

Copyright @ 2019 Macrosoft Inc