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

Couldn't stay away from this for too long.

(Part I here)

I deleted the folder and started over.

1) Started VS as administrator
2) Created Web API Project without a test project
3) Compiled right away and it worked!
4) Updated all packages via NuGet
5) Compiled and it still worked!
6) Added my EDMX model again (had to do the Azure path all over again)
7) Compiled and it still works!
8) Chcked in the code into TFS

9) On a different computer I cheked out the code.
10) Compiled and it didn ... no it worked!
11) I hit F5 and .... NOOOOOOOOOOOOOOOO!!!!!!!!!

Could not load file or assembly 'Newtonsoft.Json, Version=4.5.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

12) This time the web.config fix worked

      <dependentAssembly>

        <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />

        <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" />

      </dependentAssembly>

Again ... I thought that .NET was supposed to fix all this! As there are more and more versions, it seems to be worse than ever before. It's such a fragile system.

Alot of good things are coming out of Microsoft lately -- so far Azure ROCKS!!!! So hopefully all this will be worked out as well. Part of the issue is the lack of transparancy -- who knows where these references are coming from.