Could not load file or assembly 'AutoMapper' or one of its dependencies. Strong name signature could not be verified.

[arex388]

Since I saw that you're targeting .NET Standard 2.0 again, I thought I could finally upgrade from v10.1.1 on my ASP.NET MVC 5 project on .NET Framework 4.8. While the project does build without any complaints, when I try to run the app locally via IIS, I get the following exception:

Warning

Could not load file or assembly 'AutoMapper' or one of its dependencies. Strong name signature could not be verified. The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)

I thought it was the binding redirects, but they should be fine:

<dependentAssembly>
	<assemblyIdentity name="AutoMapper" publicKeyToken="be96cd2c38ef1005" culture="neutral" />
	<bindingRedirect oldVersion="0.0.0.0-15.0.0.0" newVersion="15.0.0.0" />
</dependentAssembly>

The IIS AppPool does target .NET v4.0. Is there something else I need to be doing or is this an issue with how the NuGet package was deployed?

[BlaiseD]

Seeing the same thing. It works in some cases but not for xUnit for example. I belive .netStandard is being public signed unintentionally.

Repro:

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <TargetFramework>net472</TargetFramework>
    <ImplicitUsings>enable</ImplicitUsings>
    <Nullable>enable</Nullable>

    <IsPackable>false</IsPackable>
    <IsTestProject>true</IsTestProject>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="AutoMapper" Version="15.0.0" />
    <PackageReference Include="coverlet.collector" Version="6.0.0" />
    <PackageReference Include="Microsoft.NET.Test.Sdk" Version="17.8.0" />
    <PackageReference Include="xunit" Version="2.5.3" />
    <PackageReference Include="xunit.runner.visualstudio" Version="2.5.3" />
  </ItemGroup>

  <ItemGroup>
    <Using Include="Xunit" />
  </ItemGroup>

</Project>

    public class UnitTest1
    {
        [Fact]
        public void Test1()
        {
            try
            {
                var assembly = Assembly.Load("AutoMapper, Version=15.0.0.0, Culture=neutral, PublicKeyToken=be96cd2c38ef1005");
            }
            catch (Exception ex)
            {
                throw;
            }
        }
    }

What works:
Reference the local build directly and replace:

<PackageReference Include="AutoMapper" Version="15.0.0" />

with

    <Reference Include="AutoMapper">
      <HintPath>..\..\..\LuckyPennySoftware\AutoMapper\src\AutoMapper\bin\Debug\netstandard2.0\AutoMapper.dll</HintPath>
    </Reference>

To reproduce the error locally (on windows): In AutoMapper.csproj replace:

<PublicSign Condition=" '$(OS)' != 'Windows_NT' ">true</PublicSign>

with

<PublicSign Condition=" '$(OS)' == 'Windows_NT' ">true</PublicSign>

rebuild and try again.

[jbogard]

Ahhhh yes, the netstandard2.0 version should not be public signed. Only net8.0 etc. I'll get a fix out ASAP.

[jbogard]

Actually, I don't think that PublicSign business is needed at all. Just going to remove it.

[jbogard]

@BlaiseD I don't actually have a Windows machine so I couldn't reproduce this locally (it didn't fail in Parallels, no idea why). But the sn.exe tool showed that the strong name was not valid for the netstandard2.0 version before I removed the public sign business.

I think this one came about because I switched some of the build images a while back to Ubuntu.

[BlaiseD]

@BlaiseD I don't actually have a Windows machine so I couldn't reproduce this locally (it didn't fail in Parallels, no idea why). But the sn.exe tool showed that the strong name was not valid for the netstandard2.0 version before I removed the public sign business.

I think this one came about because I switched some of the build images a while back to Ubuntu.

Makes sense. I can confirm it is resolved now in v15.0.1.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.