It shouldn't be this hard .... (part III)

Just when you thought it was safe to go back into VS....

(Part II here)

All I did was add some scaffolled OData controllers, added all my tables to the WebApi.Config and pressed F5.

Could not load file or assembly 'System.Web.Http, Version=5.0.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)

Line 35:             config.Routes.MapODataRoute("odata", "odata", builder.GetEdmModel());
Line 36: 
Line 37:         }

Really?

The build output has this:

1>  Consider app.config remapping of assembly "System.Net.Http.Formatting, Culture=neutral, PublicKeyToken=31bf3856ad364e35" from Version "5.0.0.0" [] to Version "5.1.0.0" [D:\Lieb-Tech\packages\Microsoft.AspNet.WebApi.Client.5.1.1\lib\net45\System.Net.Http.Formatting.dll] to solve conflict and get rid of warning.

1>  Consider app.config remapping of assembly "System.Web.Http, Culture=neutral, PublicKeyToken=31bf3856ad364e35" from Version "5.0.0.0" [] to Version "5.1.0.0" [D:\Lieb-Tech\packages\Microsoft.AspNet.WebApi.Core.5.1.1\lib\net45\System.Web.Http.dll] to solve conflict and get rid of warning.

1) There's no app.config, as this is a web project.

2) Why not provide some link to a help document to explain this issue?

.NET is like a box of chocolates. Can't wait until I get the next dependancy/version/etc error.