fluffynuts commented on pull request #18: URL: https://github.com/apache/logging-log4net/pull/18#issuecomment-1035938068
@tobylo I've been looking into this as part of another issue - there's a similar situation in the "non-log4j" variant which I had to update for the test app I wrote to work against it since the test app is using dotnet 6. I have updates in the pipeline that use the merged behavior for the NETSTANDARD target only, reverting to the original behavior otherwise, which should solve the problem for both use-cases. This is an unfortunate case of dotnet breaking compatibility - older `XmlWriter.WriteStartElement` calls would allow element names with a `:` in them (ie `log4j:event`) where dotnet core / 5+ throw an argument exception for this and provide no way to request the original behavior - instead, you have to go all-in on namespacing. I don't know when I'll get a release out because I was working on this to solve another issue (issue claims that there's a circumstance where logs are overwritten instead of rolled, and the example provides uses the other xml layout class). Perhaps it's worthwhile doing a fix release _just_ to get this behavior out? Your thoughts? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
