As described in Custom VB6 Language Replacement, gmStudio allows users to modify the system metalanguage files that control how the tool recognizes, interprets, and authors code. This is done by configuring the tool to use a project-specific copy of the default metalanguage files. However, product updates frequently include changes to the default metalanguage files, so care must be taken to make your modified files remain compatible with the system defaults. The Configuration Form facilitates this by helping you compare and merge the system default files with your project-specific files. This can also be helpful if you want to review changes or remove a change from your project specific files.
The steps for getting back in sync are as follows:
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.
An alternative to making project-specific copies of metalang source files is to use a mig.VB7Lang.xml file. See the example here: Custom VB6 Language Replacement#Example:ChangingtranslationofValforVB.NET