XMLWordPrintable

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 2.4.8
    • Fix Version/s: 2.5.0
    • Component/s: library
    • Labels:
      None

      Attachments

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

        Activity

        Hide
        jmorris Jeff Morris added a comment - - edited

        Upgrading the SDK means going from supporting netstandard1.5 to netstandard2.0; there are trade-offs when considering which netstandard to support:

        "When choosing a .NET Standard version, you should consider this trade-off:

        • The higher the version, the more APIs are available to you.
        • The lower the version, the more platforms implement it.

        In general, we recommend you to target the lowest version of .NET Standard possible. So, after you find the highest .NET Standard version you can target, follow these steps:

        1. Target the next lower version of .NET Standard and build your project.
        2. If your project builds successfully, repeat step 1. Otherwise, retarget to the next higher version and that's the version you should use."

        Because the SDK is a lower level component and because we want to support the most platforms possible, we will stay with netstandard1.5. 

        The assemblies/projects (linq2Couchbase, Couchbase.Extensions, etc.) which depend upon SDK can support a higher netstandard, so those projects will be updated to a higher netstandard if possible.

        Note: the current SDK has been proven to be compatible with projects that are using .NET Core 2.0!

        Show
        jmorris Jeff Morris added a comment - - edited Upgrading the SDK means going from supporting netstandard1.5 to netstandard2.0; there are trade-offs when considering which netstandard to support : "When choosing a .NET Standard version, you should consider this trade-off: The higher the version, the more APIs are available to you. The lower the version, the more platforms implement it. In general, we recommend you to target the lowest version of .NET Standard possible. So, after you find the highest .NET Standard version you can target, follow these steps: Target the next lower version of .NET Standard and build your project. If your project builds successfully, repeat step 1. Otherwise, retarget to the next higher version and that's the version you should use." Because the SDK is a lower level component and because we want to support the most platforms possible, we will stay with netstandard1.5.  The assemblies/projects (linq2Couchbase, Couchbase.Extensions, etc.) which depend upon SDK can support a higher netstandard, so those projects will be updated to a higher netstandard if possible. Note: the current SDK has been proven to be compatible with projects that are using .NET Core 2.0!

          People

          • Assignee:
            jmorris Jeff Morris
            Reporter:
            jmorris Jeff Morris
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes

                PagerDuty

                Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.