RestSharp nuget Assembly version (105.2.3.0) vs RestSharpSigned Assembly version (100.0.0.0)

First of all, sorry in advance as I know the signed version is not a priority.

Hi - When I install RestSharpSigned via nuget the project reference is added as:

<Reference Include="RestSharp, Version=**100.0.0.0**, Culture=neutral, PublicKeyToken=598062e77f915f75, processorArchitecture=MSIL">
     <HintPath>..\..\packages\RestSharpSigned.105.2.3\lib\net452\RestSharp.dll</HintPath>
     <Private>True</Private>
   </Reference>

When installing RestSharp project reference looks like:

<Reference Include="RestSharp, Version=**105.2.3.0**, Culture=neutral, processorArchitecture=MSIL">
      <HintPath>..\..\..\packages\RestSharp.105.2.3\lib\net452\RestSharp.dll</HintPath>
      <Private>True</Private>
    </Reference>

Is it intentional to have the version 100.0.0.0 on the signed dll or a mistake?

I know I can get round it using assembly bindings, but thought I would ask as I have been getting errors looking for version 100.0.0 file and took me a while to realise the only place that’s mentioned is in the dll itself and the project references, everything else refers to 105.2.3

I’ve attached the what you see in the headers of the 2 dlls when decompiling them. RestSharp.dll (unsigned) RestSharp.dll (signed)

Thanks for any info (and also thanks for maintaining a signed version, really helps)

John

[alexeyzimarev]

Yeah, I am aware of that. I will consider to stop signing in the next major version. I can always refer to this document and say “Microsoft told me so” 😃

[mynkow]

Here is a good read => https://github.com/dotnet/corefx/blob/master/Documentation/project-docs/strong-name-signing.md