Octopus.Client-3.5.1 missing strong name verification

Legacy Uncategorised
1

By policy, we have strong-name verification enabled, what version of Octopus.Client nuget has strong name signing? This is our runtime error:

Could not load file or assembly ‘Octopus.Client, Version=3.5.1.0, Culture=neutral, PublicKeyToken=null’ or one of itsdependencies. A strongly-named assembly is required.

2

Hi Michael,

Thanks for getting in touch!

Unfortunately, we don’t have any strongly named version of Octopus.Client, so you would have to unpack the dll, sign it and then repack it.

Sorry if this is not the answer you are after, but unfortunately this is not something we are looking at doing.

Thank you and best regards,
Henrik