Closed bcallister closed 4 years ago
Will look in to this and update you.
Are you code signing your binary/application by any chance?
Nuget currently does not allow signed applications to import unsigned dependencies, which would produce this error.
If you can confirm this is the case, I can look in to getting the InterFAX package signed so you can call it.
CC/ @sdominInterfax
Yes, this is the case. I would assume most devs releasing production software are in the same boat. For example, Windows Store apps require your packages be signed. Many thanks for helping get a signed version of the InterFAX package.
Cheers!
Ben
From: Kaelan Thijs Fouwels notifications@github.com Sent: Wednesday, November 21, 2018 2:53:20 PM To: interfax/interfax-dotnet Cc: Ben Callister; Author Subject: Re: [interfax/interfax-dotnet] Fix: InterFAX.Api does not have a strong name... (#20)
Are you code signing your binary/application by any chance?
Nuget currently does not allow signed applications to import unsigned dependencies, which would produce this error.
If you can confirm this is the case, I can look in to getting the InterFAX package signed so you can call it.
CC/ @sdominInterfaxhttps://github.com/sdominInterfax
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/interfax/interfax-dotnet/issues/20#issuecomment-440805123, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AbaR9OXQNT_zLu-gi9OVnFG1iYr9IN3pks5uxb1AgaJpZM4Yoakx.
Hi Kaelan, I am not code signing. Thank you very much for helping with the library.
A signed version of client 3.1.4 is now available that should resolve this issue.
glad we finally fixed this 😂😂
My project complains when building with the InterFAX.Api assembly. Below is the error:
"Referenced assembly 'InterFAX.Api, Version=3.0.1.0, Culture=neutral, PublicKeyToken=null' does not have a strong name."
Can you please resolve this and post an updated version to Nuget? Many thanks.