Question

I am building an application that calls upon a compiled executable. Said executable’s source code project file is referenced by the solution file for the parent application. The child executable is a stand alone command line application. The parent is a effectively a GUI wrapper to the console application. When I compile the console application, I have access to all of log4net’s functionality that has been built into the application. However, when I compile the parent project that references the console application’s source code files, everything runs correctly but no logs are generated. What would cause this error to occur, and how can this occurrence be fixed? log4net’s internal debugging mechanism doesn’t throw any messages.

Answer 1

For log4net to start logging within the referenced assembly you will have to:

• Call the Configure() function of log4net by either calling log4net.Config.XmlConfigurator.Configure() when your application starts, or by adding [assembly: log4net.Config.XmlConfigurator(Watch=true)] to the AssemblyInfo.cs file of your wrapper application.
• Create an log4net configuration section in the app.config for your GUI wrapper if you haven’t already done so. Add an app.config file to your project, and copy your log4net configuration information from the referenced library into it.
• Ensure that the account running the application has access to write and create files within the log directory (assuming your using file-based logging).

For more info about setting up your config see: http://logging.apache.org/log4net/release/manual/configuration.html