Set Copy Local to true in the properties for the System.Web.Http and System.Web.Http.WebHost assemblies and redeploy the package. If this doesn’t solve your problem completely try reinstalling the NuGet package. This will hopefully correct broken dependencies. From the package management console, run this command: Update-Package Microsoft.AspNet.WebApi -reinstall Make sure to install System.Web.Http.WebHost as well.
Going into Internet Explorer –> Tools –> Internet Options –> Browsing History,Delete…, , checking Temporary Internet Files and clicking delete fixed my issue. Thanks to this blog post: http://www.request-response.com/blog/CommentView,guid,9f383687-3e1e-4568-833b-ef80e0938337.aspx
Just to supplement with a little more precise answer: You need to either run FxCopCmd.exe with: fxcopcmd.exe /assemblyCompareMode:StrongNameIgnoringVersion or modify your Visual Studio project file for each build configuration’s property group, like this: <PropertyGroup Condition=” ‘$(Configuration)|$(Platform)’ == ‘Release|AnyCPU’ “> … <CodeAnalysisAdditionalOptions>/assemblyCompareMode:StrongNameIgnoringVersion</CodeAnalysisAdditionalOptions> </PropertyGroup>
No, it is not possible. The assemblies need to have the same publicKeyToken. The bindingRedirect tag only has the oldVersion and newVersion attributes, so there’s no way to tell it about the “null” version anyway. But the real reason behind is explained due to the strong name mechanism
A good place to start your investigation into any failed binding is to use the “fuslogvw.exe” utility. This may give you the information you need related to the binding failure so that you don’t have to go messing around with any registry values to turn binding logging on. Fuslogvw MSDN page The utility should be … Read more
Does this mean if I have a web project that depends on a class library and that class library has a reference to an older version of the assembly which has a a bindingRedirect, that the code will execute as if it were compiled against the newer version? You have it right (I would just … Read more