485
edits
Upgrading workspaces to a newer Visual DataFlex version: Difference between revisions
Upgrading workspaces to a newer Visual DataFlex version (view source)
Revision as of 15:44, 18 December 2008
, 18 December 2008→Smooth upgrades
| Line 22: | Line 22: | ||
Check them and see if they make sense. If they do make sense, then '''make the correction in the source workspace'''. | Check them and see if they make sense. If they do make sense, then '''make the correction in the source workspace'''. | ||
Yes you read that correctly by making your source workspace more compliant to the wizard, you make your life ALOT easier. | Yes you read that correctly by making your source workspace more compliant to the wizard, you make your life ALOT easier. | ||
When you've identified all of the problems (and made many changes to your source workspace) do check your changes into your version control code system of choice. | When you've identified all of the problems (and made many changes to your source workspace) do check your changes into your version control code system of choice. (*) | ||
When you are done with removing the warnings.. don't finish the wizard (or delete the results) but instead rerun the wizard. Check that your edits have improved the migration wizards result. | When you are done with removing the warnings.. don't finish the wizard (or delete the results) but instead rerun the wizard. Check that your edits have improved the migration wizards result. | ||
| Line 31: | Line 31: | ||
Congratulations, you have now offloaded some upgrade pains to your current workspace and even if you do not get the chance to upgrade now (time constraints) your life will be easier the next time when you do get a chance. | Congratulations, you have now offloaded some upgrade pains to your current workspace and even if you do not get the chance to upgrade now (time constraints) your life will be easier the next time when you do get a chance. | ||
Not only this, but when you do start the actual migration, your codebase won't change that much, making it easier to track the upgrade changes. | Not only this, but when you do start the actual migration, your codebase won't change that much, making it easier to track the upgrade changes. | ||
(*) If you do not use a version control system yet, then do yourself a real pleasure and use file comparison software to make sure that there are no unintended edits! Better even, go get yourself on version control now! | |||
==== Tips for speeding it all up ==== | ==== Tips for speeding it all up ==== | ||