MG65Migration-Migrating Applications
From MapGuide Best Practices Wiki
Once the maps have been created and assuming development platform and server architecture have been selected and set up, the developer can then begin the process of migrating the application. This process is the most time-consuming portion of the migration. The list of functions identified in the plan is important to the development process. The list should be refined to reflect any functionality that can be eliminated by using out-of-the-box Autodesk MapGuide Enterprise functionality.
The most crucial functionality to be migrated is object selection and interaction with the server, Zoom GoTo functionality, and reporting. These functions are the ones most commonly used in Autodesk MapGuide applications.
Developers can take one of two approaches to writing the actual code for the site. Developers can either start from scratch and write the entire code base and integrate either the new design or the old one into the application. Or the developer can duplicate the existing application and modify it by deleting old code and adding new code. It is up to the developer as to which approach works best, but starting from scratch could be more efficient since the API is completely different and none of the old API calls can be reused.
