'Different NLog Instance In Order to Separate NLog configuration in different config files
Currently i am facing NLog.Configuration overwritten issue if i point LogManager.Configuration to different config file.
Is it possible to create multiple NLog instance in same project to prevent sharing same LogManager.Configuration?
Something like :
FruitType class has own NLog instance, its NLog.LogManager.Configuration is read from default nlog.config.
Then, i would like to configure sub-class to be something as follow:
Apple class instance has own NLog instance and Apple class NLog.LogManager.Configuration is read from AppleNLog.config instead of nlog.config.
then new fruit
Orange class instance has own NLog instance and Orange class instance NLog.LogManager.Configuration is read from OrangeNLog.config instead of nlog.config.
The reason i want to do this is to separate the nlog rule into different config file instead of default nlog.config to micro-manage nlog configuration.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|
