Console Application and missing Log File when using WriteTo.File()

Question

I've written a C# console application that is being called by another program when that program completes.

My application is quite simple in that it accepts a number of command line arguments and then does some processing. I've added Serilog today in order to produce a log file instead of using the Console to display progress.

The application works, it does what it should and is feature complete. The following is how I create serilog:

Log.Logger = new LoggerConfiguration()
                .MinimumLevel.Information()
                .WriteTo.Console()
                .WriteTo.File("logfile-.txt", rollingInterval: RollingInterval.Day)
                .CreateLogger();

and I have Log.Debug/Warning/Information/Error where needed in my code.

If I run my code in debug or when I run it on the destination computer myself I can see the log appear in the console window and a logfile-.txt file is created with the output.

However the issue(s) I'm experiencing is when I build in release or debug and when the parent program calls it after it completes it's action my program runs, executes and does what it does but no log file is created or appended to.

As the program creates the log file when I or an administrator runs it I think it may be a permissions issue. I've tested with giving both the parent application and my application "run as administrator" permissions to no avail. Even giving EVERYONE full access to the folder where my program resides didn't result in a log file being created.

Would anyone know of something else I could look at or is there an option in serilog where I could look for it's own log when it is running in case there is an error that I'm not seeing?

Thank you,

Phil.

Edit #1:

I've been researching further and I've added the following to my Program:

Serilog.Debugging.SelfLog.Enable(new StreamWriter("serilog.txt"));

Compiled in both Release and Debug and if I run the program serilog.txt appears but if the parent application calls my program it does not.

Edit #2

Further researching led me to this question where the answer, for the OP (david w) was to add something to a .json file but I can't see a file in my project that matches that and I'm not 100% sure it applies to me.

I'm at a loss where to go next, any suggestions appreciated (and upvoted, when I can)

Answer 1

The problem turned out to be my assumption of where the log was being written to was not correct. I've modified my code to write the log to the folder where my EXE is (and where it should have access):

.WriteTo.File(Path.Combine(Path.GetDirectoryName(System.Reflection.Assembly.GetExecutingAssembly().Location), _logfilename), shared: true, rollingInterval: RollingInterval.Day)

Thanks to all for the help.