RT0999: Could not load file or assembly 'System.ServiceModel.Primitives' with NET Standard 2.0

Question

RT0999: Could not load file or assembly 'System.ServiceModel.Primitives' with NET Standard 2.0

vmcbaptista opened this issue 3 years ago · comments

I have a .NET Standard 2.0 project, <Project Sdk="Microsoft.NET.Sdk">

referencing the following nuget
<PackageReference Include="System.ServiceModel.Primitives" Version="4.8.1" />

I'm getting the following error during build
1>Reinforced.Typings : Unexpected error RT0999: Could not load file or assembly 'System.ServiceModel.Primitives, Version=4.8.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.

The same happens if I retarget the project to .net core or .net 5.

If I retarget the project to .net framework, build runs fine

Christoph J. · Answer 1 · Wed Mar 02 2022 14:48:53 GMT+0800 (China Standard Time)

Any updates here? I have the same problem with .net 5

BeigeBox · Answer 2 · Fri Jul 29 2022 00:49:03 GMT+0800 (China Standard Time)

@vmcbaptista @Crossfire92 Did either of you figure out what the cause was, or a workaround?

Norbert Virth · Answer 3 · Fri Jul 05 2024 17:03:23 GMT+0800 (China Standard Time)

I'm also interested, we have this now in a .net 8 project when adding <RtAdditionalAssembly> to a project referencing System.ServiceModel.Primitives

1>Reinforced.Typings: Warning RT0014 Assembly loading: Assembly System.ServiceModel.Primitives (from C:\Users\xxx.nuget\packages\system.servicemodel.primitives\6.2.0\ref\net6.0\System.ServiceModel.Primitives.dll) failed to load: System.BadImageFormatException: Could not load file or assembly 'System.ServiceModel.Primitives, Version=6.2.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL'. Reference assemblies cannot be loaded for execution. (0x80131058)

Norbert Virth · Answer 4 · Mon Jul 22 2024 22:37:59 GMT+0800 (China Standard Time)

Fixed in previous PR, turns out there are so called "Reference Assemblies" which are stripped-down versions of the actual implementation assemblies, and some nuget packages ship them in their /ref/ folders.
And also ship the corresponding real assembly in the /lib/.

My solution was to use the normal assembly where it could be found simply, or drop the ref assembly where not.

When building my .NET8 project, there were 311 reference assemblies (listed in the .tmp file), only 1 of them caused problems, and only 10 of them could be replaced by its implementation assembly.