Uploaded image for project: 'Couchbase .NET client library'
  1. Couchbase .NET client library
  2. NCBC-233

Enhance packaging to not conflict with other tools that include Enyim.Caching via Nuget

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.2.1
    • Fix Version/s: 1.3.0
    • Component/s: library
    • Labels:
      None

      Description

      The CouchbaseClient nuget package includes Enyim.Caching which causes compatibility issues with 3rd party applications also relying on the Enyim.Caching assembly.

      The third party tool we were looking at using was ServiceStack's Caching interface, specifically the Memcached client implementation. This tool was where were were getting the conflict as they include the Enyim.Caching assembly as a nuget dependency.

      See also http://www.couchbase.com/issues/browse/CBSE-412

      No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

        Hide
        avsej Sergey Avseyev added a comment -

        Not sure if it is related, but IMHO it is

        http://www.couchbase.com/forums/thread/please-use-nuget-correctly

        > Your NuGet packages have several problems.
        > 1. You take binary dependencies on other things which are available via NuGet, but you're shipping those binaries yourself. You should be taking a package dependency instead, so that things can be referenced and versioned correctly.
        > 2. Your "Couchbase with Logging" package should be an additive package that takes a package dependency on your "Couchbase" package, rather than shipping an entirely separate copy of the assembly. This causes linking conflicts.

        Probably it worth to increase priority of this issue

        Show
        avsej Sergey Avseyev added a comment - Not sure if it is related, but IMHO it is http://www.couchbase.com/forums/thread/please-use-nuget-correctly > Your NuGet packages have several problems. > 1. You take binary dependencies on other things which are available via NuGet, but you're shipping those binaries yourself. You should be taking a package dependency instead, so that things can be referenced and versioned correctly. > 2. Your "Couchbase with Logging" package should be an additive package that takes a package dependency on your "Couchbase" package, rather than shipping an entirely separate copy of the assembly. This causes linking conflicts. Probably it worth to increase priority of this issue
        Hide
        avsej Sergey Avseyev added a comment -

        http://www.couchbase.com/forums/thread/please-stop-using-private-build-restsharp-couchbase-net-client

        > You are currently shipping an unsigned but otherwise identically named DLL called RestSharp, which conflicts with anybody who actually uses the real shipping version of RestSharp.
        > Either use the signed production version of RestSharp, or else rename the assembly so it does not collide with the real version of RestSharp.

        Show
        avsej Sergey Avseyev added a comment - http://www.couchbase.com/forums/thread/please-stop-using-private-build-restsharp-couchbase-net-client > You are currently shipping an unsigned but otherwise identically named DLL called RestSharp, which conflicts with anybody who actually uses the real shipping version of RestSharp. > Either use the signed production version of RestSharp, or else rename the assembly so it does not collide with the real version of RestSharp.
        Hide
        john John Zablocki (Inactive) added a comment -

        This is actually being addressed in NCBC-247.

        Show
        john John Zablocki (Inactive) added a comment - This is actually being addressed in NCBC-247 .
        Hide
        jmorris Jeff Morris added a comment -

        This should be resolved, along with all Nuget packages in the 1.3.0 release. If not, please open a new ticket with a detailed description of the issue.

        Show
        jmorris Jeff Morris added a comment - This should be resolved, along with all Nuget packages in the 1.3.0 release. If not, please open a new ticket with a detailed description of the issue.

          People

          • Assignee:
            jmorris Jeff Morris
            Reporter:
            perry Perry Krug
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes