Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

gmStudio releases frequently include changes to the meta language files that control how the product recognizes, interprets, and authors source code.

If your team has customized copies of the metalanguage files, as described here, you will have to sync up your custom metalanguage files to be compatible with gmStudio release. The steps for getting back in sync are as follows:

Make a backup of your project-specific files before starting the merge so you can use it to restart if you make a mistake and to double check your work. 
For each of new system default files, check to see if you are using a custom script in your project work space. If you have a custom copy of a script, merge the new system default into your custom copy. Using a file comparison tool such as Beyond Compare.
Once you have synced all of your custom metalanguage scripts with the new system default script, rebuild your project specific metalanguage file. 
Be careful not to change the system default files when you are doing the merge.

Always keep your migration solution, including the installer for gmStudio you under version control.

  • No labels