Closed CharliePoole closed 1 year ago
It turned out to be simpler to just move the logging code into the extensibility assembly, which is referenced by both the engine and the agents.
:tada: This issue has been resolved in version 2.0.0-alpha7 :tada:
The release is available on:
This new assembly needs ot have logging but if we do it in the obvious way, based on what we have done before, it will create yet another log file.
By preference, we should pass the internal trace settings, including the writer, into the new assembly when we create ExtensionManager. To do that, InternalTrace class needs to create a singleton instance rather than being a static class.See UPDATE below