4,107 questions
Could not load file or assembly 'Microsoft.Owin, Version=4.1.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(35.2, 82%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERB%3C/text%3E%3C/svg%3E)
Rajesh Bargode
20
Reputation points
I have dot net 4.7.2 framework application. I want to update Microsoft.Owin package from 4.1.1 to 4.2.2. I have changed it through nuget package manager. It is building successfully in local but when I run it it giving me error 'Could not load file or assembly 'Microsoft.Owin, Version=4.1.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)'.
Developer technologies | .NET | Other
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(230.39999999999998, 93%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBG%3C/text%3E%3C/svg%3E)
Ben Gimblett 4,560 Reputation points Microsoft Employee2024-03-12T11:32:11.9933333+00:00 Hi - Thanks for the question. This is almost always caused by a mismatch of binaries - in other words your local bin doesn't match the bin for the deployment
In this case the application is still looking for version 4.1.1.0 so one or more assemblies still has this reference in the manifest and probably the version deployed is 4.2.2.1 hence the error
In the past I've found assembly informational versioning ,which is a label (for the assemblies I build) in addition to assembly versioning , useful in helping to troubleshoot these sorts of issues because it gives me a "by eye" view of the dll versions in my bin folder
REF
https://learn.microsoft.com/en-us/dotnet/standard/assembly/manifest
https://learn.microsoft.com/en-us/dotnet/standard/assembly/view-contents
https://learn.microsoft.com/en-us/dotnet/standard/assembly/versioning -
Rajesh Bargode 20 Reputation points
2024-03-12T11:59:02.8533333+00:00 Can you please suggest possible ways to resolve this issue?
-
Ben Gimblett 4,560 Reputation points Microsoft Employee
2024-03-12T12:06:40.9966667+00:00 Hi @Rajesh Bargode you can either rebuild with a label (file version not assembly version) and re-deploy - this will give you a by eye view - or check the manifest of the deployed assembly (or assemblies) referencing owin to see which one is not correctly updated
The other thing - if its all good locally and you trust the build you can deploy a "clean build" into a new folder. Often issues occur where you deploy into an existing folder which can leave some older files
I'm assuming there's no use of windows global assembly cache (GAC) here.
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous2024-03-13T14:52:04.1733333+00:00 Hi @Rajesh Bargode ,Is there any update in this issue?
-
Rajesh Bargode 20 Reputation points
2024-03-14T06:26:52.3066667+00:00 @Anonymous , Same issue still
-
Anonymous
2024-03-14T09:25:56.5333333+00:00 Hi @Rajesh Bargode , Welcome to Microsoft Q&A,
Are you sure you tried Clean Buil? Or try clearing the previous reference and adding it again. Another way to test is to create a simple program for Microsoft.Owin package 4.2.2 to test whether it works.
Sign in to comment
Sign in to answer