We have an application, which can use 3rd part DLLs.
We use Nlog for logging, but we have problems when using 3rd part DLLs which also uses NLOG.
They will get out instance and our configuration, and then we get some really interesting logging, not to mention that the hole thing may crash if our NLog extension is not copied to the 3rd part folder.
Other times the 3rd (or even 4th) part DLL loads its own configuration which then cancels out our logging.
How can we have our private log and/or configuration, while 3rd part DLLs can still run with their on Nlog?
I can only change our software, as we obviously have no access to 3rd part software.