given the recent deprecation of Starter service in B4XPages projects, i'm thinking about possible strategies for migrating existing projects.
rather than a "big-bang" migration (i.e: moving all the code from Starter service to other classes) i'd rather prefer a "step-by-step" strategy, where migration happens one feature a time, until the Starter service is completely empty and can be safely removed.
in this context, what is the behavior of the Application_Error sub?
can it be moved to Main module while the Starter service is still in place, or should it be the last feature to be migrated, at the same time of the Starter service removal?
rather than a "big-bang" migration (i.e: moving all the code from Starter service to other classes) i'd rather prefer a "step-by-step" strategy, where migration happens one feature a time, until the Starter service is completely empty and can be safely removed.
in this context, what is the behavior of the Application_Error sub?
can it be moved to Main module while the Starter service is still in place, or should it be the last feature to be migrated, at the same time of the Starter service removal?