Having just upgraded to Umbraco 7.7 I'm seeing an error with Microsoft.Owin when testing the builds on our servers...
Could not load file or assembly 'Microsoft.Owin, Version=2.1.0.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)
Seems that Miniprofiler is the only binary referencing v 2.1 but it doesn't look like we're able to update Miniprofiler to v 3.1 as it's a dependancy of Umbraco ( < 3.0.0 required )
Anyone hit this problem and found a solution?
Thank you
I have not seen any direct answer to this question.
I have tried to upgrade from 6.6.13 to 7.7.13 as per someones suggestion as to a migration path. I am going manual up grades.
I get the same Microsoft Owin error. Has anyone resolved this issue.
I believe the issue was running the project with visual studio 17 rather than 15 but we ended up creating a new project and copying the build over in the end
Microsoft.Owin Version 2.1.0.0 Error
Having just upgraded to Umbraco 7.7 I'm seeing an error with Microsoft.Owin when testing the builds on our servers...
Could not load file or assembly 'Microsoft.Owin, Version=2.1.0.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)
Seems that Miniprofiler is the only binary referencing v 2.1 but it doesn't look like we're able to update Miniprofiler to v 3.1 as it's a dependancy of Umbraco ( < 3.0.0 required )
Anyone hit this problem and found a solution? Thank you
Hi Warren,
Haven't actually run into this issue myself, but you might want to take a look at Assembly Binding Redirects.
See the following article: https://forums.asp.net/t/2010163.aspx?Could+not+load+file+or+assembly+Microsoft+Owin+Version+2+1+0+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+
Let me know how it goes.
Thanks
Craig
Hello everyone,
I have not seen any direct answer to this question.
I have tried to upgrade from 6.6.13 to 7.7.13 as per someones suggestion as to a migration path. I am going manual up grades. I get the same Microsoft Owin error. Has anyone resolved this issue.
Thank you, Chris
I believe the issue was running the project with visual studio 17 rather than 15 but we ended up creating a new project and copying the build over in the end
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.