Update log4net to fix Issue #57

[CryptArchy]

Issue #57 refers to log4net causing irrecoverable version conflicts due to a change in public token. Updating to the latest version appears to cause no conflicts.

[msftclas]

Hi @CryptArchy, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

[msftclas]

@CryptArchy, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.

Thanks, MSBOT;

[tscoville2012]

Is there any timeline for this getting merged?

[ioanaanamariamarcu]

Any updates on this? We have been using this library successfully but now we have to integrate it in a large solution with plenty of dependencies to a newer version of log4net.

[CryptArchy]

I ended up abandoning the use of this project due to this and other issues. Zookeeper.NET (which this relies on) also had some issues and upgrading it proved even more arduous.

Ultimately, we wrote a simple wrapper REST API in Node.js to stand in front of Kafka and we call that with the .NET HttpClient.

Some people have suggested migrating to https://github.com/ah-/rdkafka-dotnet as well. Hopefully one of those solutions will assist you all. Good luck!

[tscoville2012]

We've moved to the https://github.com/ah-/rdkafka-dotnet project and have had a lot of success with it so far.

[ioanaanamariamarcu]

Thanks for the tip. We ended up building the Kafka and Zookeper solutions locally and directly referencing the generated dlls (pffff deadlines). We were hoping the PRs would be merged eventually (both the Kafka and Zookeeper repos have pending PRs) and we could revert to using the nuget packages, but it seems it would be a better idea to switch to the other project altogether.