Skip to main content

Strong-Named Mindee.dll & PublicKeyToken Support (.NET SDK)

Feature Request

Hi Mindee Team,

I’m using the Mindee .NET SDK (v3.37.0) in a .NET Framework (net48) application.

Our application is strong-name signed, so all referenced assemblies must also be strong-named and contain a valid PublicKeyToken. Currently, the Mindee.dll provided via NuGet is not strong-name signed.

Is a strong-named version of Mindee.dll available, or are there any plans to provide one in future releases?

Please let us know the recommended approach for environments where strong-name signing is mandatory.

Thanks.

Posted by Kavya Kavya ·
Status: Completed8 comments

Log in to comment and vote

Comments8

  • Ianaré Sévi

    Team•

    Jan 12

    Hi again,

    We’ve made the needed changes internally for adding strong name support.

    However as per the official MS guidelines we will need to do a major version otherwise we will break compatibility. We are already working on a new major version, so we will include the strong name, but this will take us a few weeks at least.

    As a result, if you need this urgently, we can build a custom package for you. I will send a private message to continue the discussion.

    • Kavya Kavya

      •

      Jan 13

      Hi Ianaré,

      Thank you for the update.

      We need this urgently, so we would like to proceed with the custom package that includes strong name support. Please let us know the next steps.

      Thanks and regards,
      Kavya

      • Sebastian Olivera Silvera

        •

        Jan 13

        Hello,

        We have released a quick strong named version (available here:

        https://www.nuget.org/packages/Mindee/3.37.1-strongname)

        Can you confirm that it works for you?

        • Kavya Kavya

          •

          Jan 14

          Hello Sebastian,

          Thank you for your support and for sharing the strong-named Mindee 3.37.1 package.
          We have integrated the new version into our application; however, we are now facing the issue described below.

          We have integrated the Mindee 3.37.1-strongname package into a .NET Framework 4.8 application.

          After referencing the DLL, we inspected its dependencies and observed the following (from the assembly references):

          • Microsoft.Extensions.Configuration.Binder 9.0.0.6

          • Microsoft.Extensions.DependencyInjection 9.0.0.6

          • Microsoft.Extensions.DependencyInjection.Abstractions 9.0.0.6

          • Microsoft.Extensions.Logging 9.0.0.6

          • Microsoft.Extensions.Logging.Abstractions 9.0.0.6

          • Microsoft.Extensions.Options 9.0.0.6

          • Microsoft.Extensions.Options.ConfigurationExtensions 9.0.0.6

          • System.Text.Json 8.0.5

          • System.Text.Encodings.Web 8.0.0

          • System.Memory 4.0.1.2

          • System.Net.Http 4.2.0.0

          Even after referencing all these dependencies manually, at runtime we encounter the following error:

          “Could not load file or assembly ‘Mindee, Version=3.37.1.0, Culture=neutral, PublicKeyToken=28e81ccd38a64fe9’ or one of its dependencies. The system cannot find the file specified.”

          This issue occurs specifically in .NET Framework 4.8 and appears to be related to dependency compatibility at runtime.

          Could you please advise on the recommended or supported dependency versions for using Mindee 3.37.1-strongname with .NET Framework 4.8, or confirm the supported framework for this package?

          Thank you for your continued support.

          Regards,
          Kavya

          • Ianaré Sévi

            Team•

            Jan 14

            Hi Kavya,

            I’m not aware of this type of error, we are looking into it.

            We do recommend using .NET 6+ but realize this is not possible for all our users.

            In any case we’ll let you know if we are able to reproduce/fix the issue.

            Thanks,

          • Ianaré Sévi

            Team•

            Jan 15

            Hi Kavya,

            We have a branch ready with fixes that should correct the problem.

            It would be best for you to take a look before we publish the fixes.

            Can you compile this branch locally to confirm the fix works for your environment?

            https://github.com/mindee/mindee-api-dotnet/pull/360

            Thank you

  • Ianaré Sévi

    Team•

    Jan 12

    Hi, and thank you for your feedback.

    This is not something we currently support, but we can certainly strong name our releases.

    I like “Leonardo”, as it means “courageous lion”, which sounds pretty strong indeed.

    More seriously, we can likely release a new version with a signed assembly within the next couple days.