Hi David, Thanks a million for taking a look.
I am sure there is little I can do to help it get released, but just in case, I will offer. Let me know if there is anything I can do to help the new version get released. In fact, let me know if there is anything I can do for log4net in general. Always wanted to be part of an open source project in a more real way. Thanks David -----Original Message----- From: Davyd McColl <dav...@gmail.com> Sent: Sunday, October 24, 2021 4:07 PM To: dev@logging.apache.org Subject: [EXTERNAL] Re: Fix for Issue Log4net-611 Hi I'll try get some time to look at this this week. There's another small fix I'd like to make and I've been putting it off because the release process is such a mission (the apache way of doing things - unlike my libraries which I can just release, log4net has to go through a vote and republish docs and so forth, even though I'm the only one maintaining it right now. Thanks for the pr - I'll try check it out tomorrow. -d On October 24, 2021 11:29:52 David Schwartz <david.schwa...@ni.com> wrote: > Hi Log4Net, > > I have a PR to repair issue 611 for .netstandard 2.0 libraries. > > https://urldefense.com/v3/__https://issues.apache.org/jira/browse/LOG4 > NET-611__;!!FbZ0ZwI3Qg!5_XHxKYCPk2rnYryApcLEuBiFixyCfmAw-Q0KQ3iIJKxLhw > a48wrMiwtrN2rVY7j_g$ > > It is a small change to the AssemblyInfo.cs to allow low trust level > for .netstandard 2.0 compilation (which is already the setting for > netframework > 4.7.2) > > https://urldefense.com/v3/__https://github.com/apache/logging-log4net/ > pull/76__;!!FbZ0ZwI3Qg!5_XHxKYCPk2rnYryApcLEuBiFixyCfmAw-Q0KQ3iIJKxLhw > a48wrMiwtrN3QAWnZ-g$ > > I need this as part of the migration plan of our products to .net > standard / .net 5. Could someone please review/approve the PR and > then release a new version of log4net with this change? > > Thank you > > David Schwartz > NI
