-
Notifications
You must be signed in to change notification settings - Fork 165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Target filename does not seem to like certain characters - NLog Asp.NET Core 4.5.3 #285
Comments
I'm a bit confused. NLog is loaded before replacing with octopus?
Which target could result in |
@oggythorpe1610 Have you checked the NLog Internal Logger to see how it parses the input? It will show the parsed layout and the filenames being created. See https://github.com/NLog/NLog/wiki/Internal-Logging |
bump @oggythorpe1610 |
see also NLog/NLog#2714 - it just works. |
Closing this due to inactivity. Please let us know if this still an issue and please provide the requested info - |
Type Bug
NLog.Web.AspNetCore version: 4.5.3
NLog.Extensions.Logging version: 1.0.1
Platform: .NET Core 2
Current NLog config (xml)
#{WebServices.Logging.Root}
are replaced by Octopus with a valid path.Current result, target filename for log files when containing braces in the path causes a log file name to be written incorrectly. So a filename of C:\Logs\UAT (Testing)\Debuglog.log will be written as C:\Logs\UAT (Testing).
Expected result, target filename should accept valid filename characters in the path so that a filename of C:\Logs\UAT (Testing)\Debuglog.log will be written as C:\Logs\UAT (Testing)\Debuglog.log.
Changing the path in the config to C:\Logs\Debuglog.log allows the correect log file to be written.
The text was updated successfully, but these errors were encountered: