Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Mar 23, 2013 12:58 AM by Pithecanthropus
Oct 16, 2012 09:09 PM|LINK
I upgraded my project from MVC3 to MVC4, and works fine locally.
Deploying to server gave me some missing dependencies so I used "Add Deployable Dependencies" in VS 2010 for "Asp.Net MVC" and "Asp.Net Web Pages with Razor syntax"
That solved the dependencies problem, but as soon I run the project (local or deployed) I get this danged error:
Could not load file or assembly 'DotNetOpenAuth.Core, Version=220.127.116.11, Culture=neutral, PublicKeyToken=2780ccd10d57b246' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT:
I dont even use no DotNetOpenAuth (no clue what it is even)
I tried advice about cleaning your solution, deleting the bin folder, etc without luck.
Seems going to have to pull an all-nighter here so any help would really be appreciated.
Oct 16, 2012 11:03 PM|LINK
followed some hunches and deleted Microsoft.Web.WebPages.OAuth.dll from the dependent assemblies folder.
works fine now....phew!
Dec 17, 2012 08:06 PM|LINK
I'm having the same problem ... how do yo usolve it ?
Dec 18, 2012 04:43 AM|LINK
Hell, I'll be guessing / lying to remember. Ran into various problems afterwards. This works locally, not on server and vice versa (make you miss MVC 1/2/3 which was SO simple)
Keep fiddling around......you'll get it and hopefully remember what you did. ;)
I eventually started a totally new project moving over bits until everything worked. If you have time for that of course....
Mar 23, 2013 12:13 AM|LINK
I didn't intentionally upgrade anything, and now I'm getting this error too, after trying to deploy it to IIS 7.0 on my Windows 2008 box
The odd thing is that on the server I'm getting the familiar 403.14 error (default document not defined). The DotNetOpenAuth.Core error is happening on my development machine, where the web app was running fine before.
Mar 23, 2013 12:58 AM|LINK
Can anyone explain why this happens? I set up my project as an (empty) ASP.NET MVC3 web applic?ation when I started it, so why would it change now? Or is it a runtime component that for some reason is only now being invoked?
I'm going to try rebooting the development machine and see if that will clear this.