On 2018-01-12, Dominik Psenner wrote: > I'm working on LOG4NET-566, hoping that we can get a release build > from our CI.
CI won't be able to create the oldkey binaries unless we are willing to make the old key public (which defeats the reason why the new key was introduced in the first place. > The build currently gets stuck because of an unknown reason. It would > be great to get some help on finding out why the heck the > netstandard-1.3 tests behave as they do here: Currently I'm not able to build .NET Standard 1.3 at all, I'll need to create a new VM for that, I guess. All my .NET Standard builds have happened on Windows in the past, maybe the issue you see is specific to Linux? Stefan
