Log4net configuration file Management

used to log4net in the past always in the tangled configuration log4net, will always occur when the configuration file does not take effect, and finally found that the configuration file is not copied to the log4net running directory, is really tangled. Now, the problem is solved by using the file as an embedded resource and then initializing it to load the next configuration file. The following methods are as follows:

1. Add the configuration file to the current. NET related project:

2. Initialize Log

        publicstaticvoid  Init ()        {            = assembly.getexecutingassembly () ;             var xml = assembly. GetManifestResourceStream ("YourNamespace.Config.Default.config");            Log4net. Config.XmlConfigurator.Configure (XML);        }

OK, then you can use the Log4net!!

Log4net configuration file Management