Ivan Kopcanski commented on ZOOKEEPER-2209:

There is an annoying issue with log4net.dll reference in projects.
zookeepernet uses log4net version has old public key token.
If your project uses log4net recent versions, it has new public key token.
Once you reference zookeepernet in your solution, it wont work,
because there will be conflict with loading log4net dll.
Environment sees these 2 versions as totally different dll-s, because of public 
key token.
Solution: Can zookeepernet use nuget package for log4net that will manage 
version collisions?

> A .NET C# version of ZooKeeper client
> -------------------------------------
>                 Key: ZOOKEEPER-2209
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2209
>             Project: ZooKeeper
>          Issue Type: New Feature
>    Affects Versions: 3.4.6
>         Environment: .NET CoreCLR
>            Reporter: Shay Hazor
>            Assignee: Shay Hazor
>              Labels: .NET, CoreCLR, async, c#
>   Original Estimate: 0h
>  Remaining Estimate: 0h
> Inspired by the work of [~ewhauser] .
> I propose a C# Client that supports the current stable version of ZK 3.4.6.
> It was built by using static code conversion tools followed by manual editing 
> and C# implementations of java selector and other java constructs. 
> A great measure was taken to follow the logic of the java version. In fact, 
> the code is almost identical. Thus allowing easy evolution alongside the java 
> version. 
> Main features:
> * fully .NET async, no explicit threads used
> * all relevant unit tests have been converted and passing consistently
> * Code is 100% CoreCLR compliant
> * [NuGet package|https://www.nuget.org/packages/ZooKeeperNetEx] is already 
> integrated in [Microsoft Project Orleans|https://github.com/dotnet/orleans] 
> as the only open-source membership provider.
> * [Nuget package for 
> recipes|https://www.nuget.org/packages/ZooKeeperNetEx.Recipes]

This message was sent by Atlassian JIRA

Reply via email to