Hello there,
We are currently using log4net for logging in our .NET Framework 4.8 application, developed with Microsoft Visual Studio Professional 2022 Version 17.12.3.
We have observed a potential issue where, when writing to a log file asynchronously, the resulting log file sometimes gets output with a duplicated file name (e.g., logfile.log.logfile.log).
We have prepared a logging configuration that mirrors our internal source code, and while we haven't been able to reproduce the issue consistently in our local testing environment, the same process in our production environment has exhibited this behavior.
We are seeking your expertise on potential causes for this duplicated file naming issue specifically in asynchronous logging scenarios within the described environment. Any insights or suggestions for investigation would be greatly appreciated.
Sincerely,
ConsoleApp.zip
Hello there,
We are currently using log4net for logging in our .NET Framework 4.8 application, developed with Microsoft Visual Studio Professional 2022 Version 17.12.3.
We have observed a potential issue where, when writing to a log file asynchronously, the resulting log file sometimes gets output with a duplicated file name (e.g., logfile.log.logfile.log).
We have prepared a logging configuration that mirrors our internal source code, and while we haven't been able to reproduce the issue consistently in our local testing environment, the same process in our production environment has exhibited this behavior.
We are seeking your expertise on potential causes for this duplicated file naming issue specifically in asynchronous logging scenarios within the described environment. Any insights or suggestions for investigation would be greatly appreciated.
Sincerely,
ConsoleApp.zip