Entityframework.docs: System.TypeLoadException

[behrooz66]

The sample code (the testing part) works perfectly in .net core 2.2, but in 3.1 it throws the following exception on the context.Database.EnsureCreated() line:

System.TypeLoadException : Could not load type 'Microsoft.EntityFrameworkCore.RelationalReferenceCollectionBuilderExtensions' from assembly 'Microsoft.EntityFrameworkCore.Relational, Version=3.1.2.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: e4f7b56f-7f91-2f15-1fb6-4f481e97534f
• Version Independent ID: 6d9c65c6-f159-b234-48fd-f25da05f0f32
• Content: Testing with SQLite - EF Core
• Content Source: entity-framework/core/miscellaneous/testing/sqlite.md
• Product: entity-framework
• Technology: entity-framework-core
• GitHub Login: @rowanmiller
• Microsoft Alias: avickers

[AndriySvyryd]

@behrooz66 That's due to a version mismatch. Check that the project references the same version of all EF packages.

[behrooz66]

@behrooz66 That's due to a version mismatch. Check that the project references the same version of all EF packages.

Going to try that and will update the results here :)

[behrooz66]

@behrooz66 That's due to a version mismatch. Check that the project references the same version of all EF packages.

Ok I can confirm that all the packages are on the same version and the exact same error is still occurring. Any other ideas?

[ajcvickers]

@behrooz66 Please post your csproj file so we can take a look.

[behrooz66]

Hi @ajcvickers , thanks for responding. Here is the xUnit test project csproj where the issue occurs:

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

  <PropertyGroup>
    <TargetFramework>netcoreapp3.1</TargetFramework>
    <IsPackable>false</IsPackable>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.EntityFrameworkCore" Version="3.1.2" />
    <PackageReference Include="Microsoft.EntityFrameworkCore.Sqlite" Version="3.1.2" />
    <PackageReference Include="Microsoft.EntityFrameworkCore.Relational" Version="3.1.2" />
    <PackageReference Include="Microsoft.NET.Test.Sdk" Version="16.5.0" />
  </ItemGroup>

  <ItemGroup>
    <PackageReference Include="xunit" Version="2.4.0" />
    <PackageReference Include="xunit.runner.visualstudio" Version="2.4.0" />
    <PackageReference Include="WireMock.Net" Version="1.1.0" />
  </ItemGroup>

  <ItemGroup>
    <ProjectReference Include="..\..\src\PNI.IdentityExpress.Service.SPLUS\PNI.IdentityExpress.Service.SPLUS.csproj" />
  </ItemGroup>

</Project>

And here is the csproj for the project that was referenced by the xUnit project;

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

  <PropertyGroup>
    <TargetFramework>netcoreapp3.1</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.EntityFrameworkCore" Version="3.1.2" />
  </ItemGroup>

  <ItemGroup>
    <PackageReference Include="Newtonsoft.Json" Version="12.0.2" />
    <PackageReference Include="PNI.IdentityExpress.Common" Version="1.1.1-rc0002" />
    <PackageReference Include="PNI.IdentityExpress.Service.Common" Version="1.0.1-rc0011" />
  </ItemGroup>

</Project>

[ajcvickers]

@behrooz66 WireMock.Net has a lot of older dependencies; it could be causing the issue. I wasn't able to find the PNI.IdentityExpress packages, so I'm not sure what dependencies these pull in.

[behrooz66]

Well the PNI.IdentityExpress is an internal package we have developed and I can guarantee it doesn't have pretty much any dependencies to pull in. But I'm not sure about WireMock.Net. I am going to try a sample without it and will update the thread after.

Aside from that, nothing else seems to be setup the wrong way, true?

[behrooz66]

OK, I was able to resolve the issue however I don't get the logic. If I have this line in the csproj of the test project, it will fail:

<PackageReference Include="Microsoft.EntityFrameworkCore" Version="3.1.2" />

Removing it solves the problem.

[ajcvickers]

@behrooz66 It's likely that your dependencies are bringing in an other EF Core and by removing that line you're no longer bringing in a new, conflicting version.