I know that deployment folders can be created to enable local server logging in order for testers to detect potential issues prior to software distribution to users. On some occasions, users call for technical telephonic assistance in running our application which renders this feature useful. However, the Runtime local server does put out an extensive amount of messages that loads logging files to maximum capacity, and deploying our application with a default deployment that has logging enabled could render systems with limited hard disk space to a bad state.
Is there a way to enable,or disable logging on already created deployment folders on demand (programmatically or manually)?
As you have probably found out by now, a deployment of LocalServer contains both a LocalServerUtility.exe and a RuntimeLocalServer.cfg file, either of which can be used to turn logging on/off.
As you have probably found out by now, a deployment of LocalServer contains both a LocalServerUtility.exe and a RuntimeLocalServer.cfg file, either of which can be used to turn logging on/off.
As you have probably found out by now, a deployment of LocalServer contains both a LocalServerUtility.exe and a RuntimeLocalServer.cfg file, either of which can be used to turn logging on/off.
