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 11 Next »

gmStudio allows users to modify the files that control how the tool recognizes, interprets, and authors code. This is done by configuring the tool to use a modified copy of the default metalanguage files. However, product updates frequently include changes to the default metalanguage files and care must be taken to make your modified files compatible with the system defaults after installing a product update.

The steps for getting back in sync are as follows:

  1. 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. 
  2. 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.
  3. Once you have synced all of your custom metalanguage scripts with the new system default script, rebuild your project specific metalanguage file. 


The Configuration Files tab on the Settings Form facilitates the process of comparing default files with project-specific files.

Please see Custom VB6 Language Replacement for more information on how to customize metalanguage files.

Be careful not to change the system default files when you are doing the merge.

It is a best practice to keep your migration solution, including all configuration files and the installers for gmStudio, under version control.

  • No labels