The Telerik Work Item Manager application uses Log4Net as its logging component. It defines a configuration section for Log4Net inside the app.config file. The problem I'm having is, we use Log4Net extensively here at this company, and we've already defined Log4Net blocks inside our machine.config files. When Work Item Manager starts up, it sees these conflicting configuration blocks and throws an exception.
Can someone explain how I can work around this to start up Work Item Manager? Perhaps there's a way to disable Log4Net for WIM so it doesn't initialize those components? It seems silly that just because I have Log4Net preconfigured on my machine that I'm not allowed to use this application.
Can someone explain how I can work around this to start up Work Item Manager? Perhaps there's a way to disable Log4Net for WIM so it doesn't initialize those components? It seems silly that just because I have Log4Net preconfigured on my machine that I'm not allowed to use this application.