Hi,
I am recently faced with a client requirement to embed a build number/code into my module ini file. I know that yeah, the webmodule object in Oscript has the '0 DumpModuleConfigToFile' function, and that we can override it to add our own tags, but what I really want is a way to have build clean regenerate the module.ini when we rebuild the module, ideally with a subclass that allows us to specify additional name=value pairs (and their section) to go into the module.ini file.
The goal is to automate this annotation that is required for the module so that product management and support know exactly what version of a module they have in their hands, as well as to automate adding items to the module.ini that may change with each subsequent build.
At the very least, the existing '0 DumpModuleConfigToFile' should be refactored so that we can override a subclass to add sections we want included additionally in the module.ini instead of having to override the entire script. Given the way that OT Dev has a tendancy to update key bits of code which 3rd party developers may orphan, this only makes sense.
-Hugh Ferguson