Closed Fungusware closed 1 year ago
This version only add a strong name to the release, so you can skip it for now. Can you elaborate on the error and give me the full exception (type, message, and if possible the stack trace)?
Has your project a strong name?
Thanks
Sorry this took so long,,,,
System.IO.FileLoadException: Could not load file or assembly 'Kveer.XmlRPC, Version=1.2.0.0, Culture=neutral, PublicKeyToken=9317cc320020ca91' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A) | File name: 'Kveer.XmlRPC, Version=1.2.0.0, Culture=neutral, PublicKeyToken=9317cc320020ca91' ---> System.Security.SecurityException: Strong name validation failed. (Exception from HRESULT: 0x8013141A) | The Zone of the assembly that failed was: | MyComputer | at XenAPI.Session.InitializeXmlRpcProxy(String url, Int32 timeout) | at XenAPI.Session..ctor(Int32 timeout, String url) in C:\Development\Fungusware\Libraries\XenServer.API\Session.cs:line 70 | at XenAPI.Session..ctor(Int32 timeout, String host, Int32 port) in C:\Development\Fungusware\Libraries\XenServer.API\Session.cs:line 79 | at XenAPI.Session..ctor(String host, Int32 port) in C:\Development\Fungusware\Libraries\XenServer.API\Session.cs:line 84 | at Xackup.Core.ServerTools.GenerateSession(String address, Int32 port, String userName, String password, String& actualHostAddress, Session existingSession) in C:\Development\Fungusware\Apps\Xackup-v2\XAckup.Core\ServerTools.cs:line 93 | at Xackup.Core.ServerTools.GenerateSession(ServerDetails server, String& actualHostAddressession, Session existingSession) in C:\Development\Fungusware\Apps\Xackup-v2\XAckup.Core\ServerTools.cs:line 35 | at Xackup.Core.JobProcessors.BaseJobProcessor.Connect() in C:\Development\Fungusware\Apps\Xackup-v2\XAckup.Core\JobProcessors\BaseJobProcessor.cs:line 168 | at Xackup.Core.JobProcessors.BaseJobProcessor.<ProcessJobAsync>d__46.MoveNext() in C:\Development\Fungusware\Apps\Xackup-v2\XAckup.Core\JobProcessors\BaseJobProcessor.cs:line 280
I have the same problem . A fix is planned? Thx
I hope yes.
I compile the release version with CircleCI; so the build is public, using a Linux container. On Linux, the sn is still not provided by Microsoft and I have to rely on mono. The sn from Microsoft and from mono differ, as mono seems to only support sha1 public token. I will use this (it is more than enough to prevent name collision, as it's the purpose of strong naming) to solve this version.
Please note that the 1.2 has no other feature than strong naming though.
That's excellent new, thanks for your efforts!
I just pushed release 1.2.1 (both github & nuget). Can you test that and confirm the library is properly signed?
Everything seems fine in the new version. I'll keep you informed if anything changes.
Regards
On Fri, Aug 11, 2023 at 2:13 AM Veovis @.***> wrote:
I just pushed release 1.2.1 (both github & nuget). Can you test that and confirm the library is properly signed?
— Reply to this email directly, view it on GitHub https://github.com/LordVeovis/xmlrpc/issues/21#issuecomment-1673685835, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVC6OG6G3AGF4WDS3JE73ETXUUQGJANCNFSM5BVGXVZQ . You are receiving this because you commented.Message ID: @.***>
John Anderson Fungusware http://fungusware.com http://www.xenserver-backup.com http://www.kojona.com
I will close this issue. Reopen if needed.
I upgraded to version 1.20 and immediately started getting a Strong Name Violation failed exception. Is there an issue with this release or am I missing something on my end.
Regards.