loggerFactory.AddLog4Net() not finding log4net.config when hosting the app in a Windows Service about microsoft.extensions.logging.log4net.aspnetcore HOT 3 CLOSED

I was able to workaround the issue... in Startup.cs => Configure method:

public void Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory)
{
    loggerFactory.AddConsole(Configuration.GetSection("Logging"));

    var pathToExe = Process.GetCurrentProcess().MainModule.FileName;
    var pathToContentRoot = Path.GetDirectoryName(pathToExe);

    // Setting the log file path and name dynamically...
    log4net.GlobalContext.Properties["LogFileName"] = pathToContentRoot + "\\Utilities.File.FileGetter.log";

    //Log4Net logging
    loggerFactory.AddLog4Net(pathToContentRoot + "\\log4net.config", true);
    loggerFactory.AddDebug();

As you see, I had to provide the path (repeat the code) used in Program.cs => Main method. Not beautiful but it works.

from microsoft.extensions.logging.log4net.aspnetcore.

Hello @leniel,

Thank you by your question and for the workaround explanation.

Please take a look into this post, that explains what is the working directory on Windows Service and how to fix this as-designed issue.

https://haacked.com/archive/2004/06/29/current-directory-for-windows-service-is-not-what-you-expect.aspx/

Regards

from microsoft.extensions.logging.log4net.aspnetcore.

@huorswords,

Adding Directory.SetCurrentDirectory(System.AppDomain.CurrentDomain.BaseDirectory); as the 1st line in Program.cs's Main method solves the issue once and for all.

Thanks for this awesome extension.

Regards,

Leniel

from microsoft.extensions.logging.log4net.aspnetcore.