When a byte or byte combination cannot be converted to a character by the
character encoding, I think Java prints '?' (0x3F) by default.
You con't need SocketAppender to reproduce this:
@Test
public void test() {
String txt = "?String" + '\uD800';
System.out.println(txt); // prints ?String
The build scripts I made and use do indeed use msbuild (or the dotnet
wrapper around it, depending on environment) - they simply abstract away
finding the latest (or requested) version as well as calling conventions.
They can also use nuget or the dotnet command for packaging and package
pushin
Great to see log4net gains some momentum! If changing the build system is
on the table, I would try sticking with the default msbuild capabilities.
Especially useful is the MSBuild inline task capability [1].
[1]
https://docs.microsoft.com/en-us/visualstudio/msbuild/msbuild-inline-tasks?view=vs-20
Hello,
While trying to understand the behavior of SocketAppender against
uncommon Unicode characters, I have come across to an interesting
case: \uD800 gets transmitted as \u003F ('?'). One can easily verify
this by appending \uD800 at the end of "This is a test message"
literals in SocketAppender
