Seems like I'm doing something stupid with the Glimpse references. I remove Glimpse (using NuGet) from my MVC 5 Visual Studio solution. I then re-add Glimpse Mvc5 1.5.2 (to just the web app project), which also adds Glimpse
ASP.NET 1.6.0 and Glimpse.Core 1.8.1. When I then do a build I get this:
2> There was a conflict between "Glimpse.Core, Version=1.8.1.0, Culture=neutral, PublicKeyToken=null" and "Glimpse.Core, Version=1.8.0.0, Culture=neutral, PublicKeyToken=null".
2> "Glimpse.Core, Version=1.8.1.0, Culture=neutral, PublicKeyToken=null" was chosen because it was primary and "Glimpse.Core, Version=1.8.0.0, Culture=neutral, PublicKeyToken=null" was not.
2> References which depend on "Glimpse.Core, Version=1.8.1.0, Culture=neutral, PublicKeyToken=null" [src\packages\Glimpse.1.8.1\lib\net45\Glimpse.Core.dll].
2> src\packages\Glimpse.1.8.1\lib\net45\Glimpse.Core.dll
2> Project file item includes which caused reference "src\packages\Glimpse.1.8.1\lib\net45\Glimpse.Core.dll".
2> Glimpse.Mvc5, Version=1.5.2.0, Culture=neutral, processorArchitecture=MSIL
2> Glimpse.Core, Version=1.8.1.0, Culture=neutral, processorArchitecture=MSIL
2> src\packages\Glimpse.Mvc5.1.5.2\lib\net45\Glimpse.Mvc5.dll
2> Project file item includes which caused reference "src\packages\Glimpse.Mvc5.1.5.2\lib\net45\Glimpse.Mvc5.dll".
2> Glimpse.Mvc5, Version=1.5.2.0, Culture=neutral, processorArchitecture=MSIL
2> References which depend on "Glimpse.Core, Version=1.8.0.0, Culture=neutral, PublicKeyToken=null" [].
2> src\packages\Glimpse.AspNet.1.6.0\lib\net45\Glimpse.AspNet.dll
2> Project file item includes which caused reference "src\packages\Glimpse.AspNet.1.6.0\lib\net45\Glimpse.AspNet.dll".
2> Glimpse.AspNet, Version=1.6.0.0, Culture=neutral, processorArchitecture=MSIL
2> Glimpse.Mvc5, Version=1.5.2.0, Culture=neutral, processorArchitecture=MSIL
It looks like Glimpse.1.8.1 and Glimpse Mvc5.1.5.2 depends on Glimpse.Core 1.8.1.0 but Glimpse.AspNet.1.6.0 depends on Glimpse.Core 1.8.0.0.
Is this correct? This causes my web deployment CI build to fail.
If I then go back to NuGet I see there is a Glimpse AspNet 1.7.0 update, so I update to that version. Now the build says:
2> There was a conflict between "Glimpse.AspNet, Version=1.7.0.0, Culture=neutral, PublicKeyToken=null" and "Glimpse.AspNet, Version=1.6.0.0, Culture=neutral, PublicKeyToken=null".
2> "Glimpse.AspNet, Version=1.7.0.0, Culture=neutral, PublicKeyToken=null" was chosen because it was primary and "Glimpse.AspNet, Version=1.6.0.0, Culture=neutral, PublicKeyToken=null" was not.
2> References which depend on "Glimpse.AspNet, Version=1.7.0.0, Culture=neutral, PublicKeyToken=null" [src\packages\Glimpse.AspNet.1.7.0\lib\net45\Glimpse.AspNet.dll].
2> src\packages\Glimpse.AspNet.1.7.0\lib\net45\Glimpse.AspNet.dll
2> Project file item includes which caused reference "src\packages\Glimpse.AspNet.1.7.0\lib\net45\Glimpse.AspNet.dll".
2> Glimpse.AspNet, Version=1.7.0.0, Culture=neutral, processorArchitecture=MSIL
2> References which depend on "Glimpse.AspNet, Version=1.6.0.0, Culture=neutral, PublicKeyToken=null" [].
2> src\packages\Glimpse.Mvc5.1.5.2\lib\net45\Glimpse.Mvc5.dll
2> Project file item includes which caused reference "src\packages\Glimpse.Mvc5.1.5.2\lib\net45\Glimpse.Mvc5.dll".
2> Glimpse.Mvc5, Version=1.5.2.0, Culture=neutral, processorArchitecture=MSIL
Now it looks like Glimpse.AspNet.1.7.0 depends on Glimpse.AspNet 1.7.0.0 (well, yeah; not even sure what that means) and Glimpse.Mvc5.1.5.2 depends on Glimpse AspNet 1.6.0.0, even though the Glimpse Mvc5 pacakage says it depends on Glimpse.AspNet 1.6.0 or later so 1.7.0 should be OK.
There seems to be a Catch-22 here. What am I doing wrong?