Page Comparison

Historically, the RTL namespace conventions employed by gmStudio were simple: almost all the support functions were implemented in a single MigrationSupport.Utils static class.  The idea was to keep it simple and easy to describe.  References , and references to these functions were expected to be temporary placeholders until alternative, custom translations were designed and implemented by the Upgrade Team as part of their Upgrade Solution.  However, we have found that some customers teams are not able to complete the analysis and design work needed for a full custom upgrade ; they only have time and funding to do produce more direct results and they are comfortable with using the RTL we provide out-of-the-box.    However, as the RTL has grown, the MigrationSupport.Utils class has become bloated.  We now find that a more structured RTL model is needed to better organize a comprehensive set of the RTL services.    To better meet this need, we are enhancing our RTL specification to allow for stubbing and using a more structured set of namespaces and classes.  The intent is to provide an a slightly more granular RTL framework that is that more descriptive and maintainable.  We are calling these new conventions gmRTL. 

The gmRTL namespace and class structure conventions will replace the legacy conventions before the end of 2021.  The legacy conventions (i.e.  MigrationSupport, MigrationSupportUI, etc) will be deprecated. 

Stay tuned for more information on the transition.