Migration Process (PowerMigrator™ – The 7 Step Process to the .NET™)

Step 1: Gathering requirements
Step 2: Generate .NET™ Forms
Step 3: Mapping FoxPro™ objects to .NET™ Objects
Step 4: Converting code to .NET™ classes and code behind
Step 5: Database conversion
Step 6: Testing Process
Step 7: Deploy

Step 1: Gathering requirements

Identify the objects in the existing application like program files, screens, reports etc. This will help to prepare the effort estimation. Based on this we will arrive the size and scope of the project.

Step 2: Generate .NET™ Forms

PowerMigrator™ tools can do the visual conversion of forms and reports. Then the converted forms and reports can be used in the .NET™ project to create a non-functioning skeleton. Also using this tool we can extend additional functionalities.

Step 3: Mapping FoxPro™ objects to .NET™ Objects

Mapping of object lies here in two major categories. One is FoxPro™ database to SQL Server database and FoxPro™ programs, screens to Visual part of the application to VB.NET™/ASP.NET™. Mapping of objects like Menu and toolbar conversion to .NET™, User inputs and output controls to .NET™

Step 4: Converting code to .NET™ classes and code behind

The common control structures are automatically converted through the tool. Just about every language has a counterpart for a control construct in every other language-or a way to emulate it. The tool also converts expressions in an automated way. - The approach we follow for converting data-specific functionality is rewriting the code as a stored procedure in the database.

FoxPro™ has default error handlers, Error () methods, ON ERROR statements, in the exception handling is done by TRY/CATCH blocks. Convert FoxPro™ reports to .NET™ reports/Crystal reports

Step 5: Database conversion

The first process of database conversion is fixing the schema in the new database. Database tuning required for fixing column type, indexes then based on the import tool, we will write the data from FoxPro™ to the SQL Server.

Step 6: Testing Process

The testing process begins on the first day of conversion and continues after write the last line of code. Unlike creating a brand-new application, conversion projects have the advantage, how the system should perform. If the new functionality matches the old functionality, it’s correct. If the new report comes out exactly the same as the old report, it’s correct. There is not the same level of work involved, as there is developing a new system and gathering and refining requirements.

Step 7: Deploy

The tested migrated .NET™ application is finally deployed to the production server.

PowerBuilder is the registered trademark of Sybase Inc.
.Net , ASP.Net , VB.Net , FoxPro are all registered trademarks of Microsoft.