Congratulations!  Your application has been migrated.

These Migration Notes are located in D:\Database\- wpc\Persons\MigrationNotes.txt

If your application was originally built using .NET Framework 2.0 or before, then it has been migrated to .NET Framework 3.5.

You may need to make additional changes to compile and run your application.
1. Search for "MIGRATION NOTES" in your .cs and .vb code-behind files and make changes as necessary.

2. Re-apply JavaScript code customizations, if any in D:\Database\- wpc\Persons\ApplicationWebForm.js
and D:\Database\- wpc\Persons\ApplicationWebUIValidation.js.

3. Re-apply style sheet changes, if any, to D:\Database\- wpc\Persons\App_Themes\Denali\Styles.css

4. If the original application contains any files and folders added by source code control software then,
during migration they will be deleted so that migration can happen smoothly. If you really need these 
files and folders then, you can check the migrated application back into the source code control system and 
it will recreate all the folders. If this does not work then you can add these folders manually from the back-up application.

5. All header/footer files have been replaced.
Re-apply any customizations you may have made to the original header/footer files 
to the new header/footer files in your application.

6. BaseApplicationPage.vb(cs) has been replaced.
Re-apply any customizations you may have made to the original BaseApplicationPage.vb(cs) files 
to the new BaseApplicationPage.vb(cs) files in your application.

7. ExportData.vb(cs) has been replaced.
Re-apply any customizations you may have made to the original ExportData.vb(cs) files 
to the new ExportData.vb(cs) files in your application.

8. FvLlsHyperLink.vb(cs) has been replaced.
Re-apply any customizations you may have made to the original FvLlsHyperLink.vb(cs) files 
to the new BaseApplicationPage.vb(cs) files in your application.

9. LargeListSelector.Controls.vb(cs) has been replaced.
Re-apply any customizations you may have made to the original LargeListSelector.Controls.vb(cs) files 
to the new LargeListSelector.Controls.vb(cs) files in your application.

10. BaseApplicationRecordControl.vb(cs) has been replaced.
Re-apply any customizations you may have made to the original BaseApplicationRecordControl.vb(cs) files 
to the new BaseApplicationRecordControl.vb(cs) files in your application.

11. BaseApplicationTableControl.vb(cs) has been replaced.
Re-apply any customizations you may have made to the original BaseApplicationTableControl.vb(cs) files 
to the new BaseApplicationTableControl.vb(cs) files in your application.

12. SignInState.vb(cs) has been replaced.
Re-apply any customizations you may have made to the original SignInState.vb(cs) files 
to the new SignInState.vb(cs) files in your application.

13. Crypto.vb(cs) has been replaced.
Re-apply any customizations you may have made to the original Crypto.vb(cs) files 
to the new Crypto.vb(cs) files in your application.

14. ImportData.vb(cs) has been replaced.
Re-apply any customizations you may have made to the original ImportData.vb(cs) files 
to the new ImportData.vb(cs) files in your application.

15. Note that during migration a lot of files such as BaseFormulaUtils.cs(vb) and many others are being replaced. For the full list of files please visit
http://www.ironspeed.com/Designer/9.2.0/WebHelp/Part_IX/Part_IX_Application_Migration.htm

16. D:\Database\- wpc\Persons\App_Code\CrPdf.vb is a custom code file that was not created by Iron Speed Designer.
If any of your application's classes or methods were used in this file, you will need to migrate them manually.

17. D:\Database\- wpc\Persons\App_Code\Ps.vb is a custom code file that was not created by Iron Speed Designer.
If any of your application's classes or methods were used in this file, you will need to migrate them manually.

Please make the 17 changes shown above before building and running your application.
You can delete the *.back files once you are satisfied with the migrated application.

For pages that contain multiple menu items, upon migration, the page will continue to display each of the menu items.
If the page is recreated after it is migrated, it will use the current default Master page, so the number of menu items displayed on the page will be based on the menu items in the current Master page.
Ideally, the additional menu items should be added to the Master page, and not to the page itself.  You can create multiple Master pages and bind pages to different Master pages as needed. 


