© 2026 Hedgehog Software, LLC

TwitterGitHubDiscord
More
CommunitiesDocsAboutTermsPrivacy
Search
Star
Setup for Free
C#C
C#•3y ago•
49 replies
zed

✅ Resolving an ambiguous assembly reference

We recently upgraded an included NuGet package from version
2.0.1
2.0.1
to
3.0.1
3.0.1
(Spring.NET, in case it matters). Now we get this exception:

Could not load file or assembly 'Spring.Services, Version=2.0.1.45000, Culture=neutral, PublicKeyToken=65e474d141e25e07' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
Could not load file or assembly 'Spring.Services, Version=2.0.1.45000, Culture=neutral, PublicKeyToken=65e474d141e25e07' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)


This indicates, that we missed upgrading one of our components, but we cannot find out which one. We're also including some third party components, which have (ostensibly) also been updated to use Spring.NET 3.0.1. But the provider assures us, that all projects in their solution were upgraded to use version 3.0.1. Now we're at a loss.

Is there a way to get more detailed information on which of our assemblies or components tries to reference the older version? A plain text search across all our
.csproj
.csproj
and
.config
.config
files revealed no reference to
2.0.1
2.0.1
, and we're not sure what else to do.
C# banner
C#Join
We are a programming server aimed at coders discussing everything related to C# (CSharp) and .NET.
61,871Members
Resources

Similar Threads

Was this page helpful?
Recent Announcements

Similar Threads

❔ Nonsense Ambiguous Reference
C#CC# / help
3y ago
Ambiguous reference with MAUI attached property
C#CC# / help
2y ago
❔ Missing assembly reference using PackageReference
C#CC# / help
3y ago
CS00012 The type is defined in an assembly that is not referenced. But that assembly it is reference
C#CC# / help
3y ago