Issue with CMS 10.8.0 nuget package update for web projects

Vote:
 

I'm trying to update a web project in our solution to EPiServer.CMS 10.8.0 from 9.12.2 and get the following error.

Unable to find a version of 'Castle.Core' that is compatible with 'Castle.Windsor 3.4.0 constraint: Castle.Core (>= 3.3.0 && < 4.0.0)', 'EPiServer.CMS.Core 10.8.0 constraint: Castle.Core (>= 3.3.3 && < 4.0.0)'. 0

Here's what I have referenced:

Castle.Core - 3.3.0.0

Castle.Windsor - 3.3.0.0

Here's my web.config assembly bindings:

<dependentAssembly>
<assemblyIdentity name="Castle.Core" publicKeyToken="407dd0808d44fbdc" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-3.3.0.0" newVersion="3.3.0.0" />
</dependentAssembly>

<dependentAssembly>
<assemblyIdentity name="Castle.Windsor" publicKeyToken="407dd0808d44fbdc" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-3.3.0.0" newVersion="3.3.0.0" />
</dependentAssembly>

#178137
May 02, 2017 18:37
Vote:
 

Just update castle core to at least 3.3.3 

#178143
Edited, May 03, 2017 2:11
Vote:
 
<p><a href="/System/Users-and-profiles/Community-Profile-Card/?userid=929d4883-19e8-e411-9afb-0050568d2da8">Aniket</a>, thanks for the reply.</p> <ol> <li>So nuget says my version installed is 3.3.3</li> <li>My assembly bindings say 3.3.0</li> <li>The version on the reference in Visual Studio is 3.3.0</li> <li>And finally the actual dll in the bin directory says 3.3.3.58</li> </ol> <p>NUGET:</p> <p>&lt;package id="Castle.Core" version="3.3.3" targetFramework="net452" /&gt;<br /> &lt;package id="Castle.Windsor" version="3.3.0" targetFramework="net452" /&gt;</p> <p>ASSEMBLY BINDINGS (no assembly binding for Castle.Windsor):</p> <p>&lt;dependentAssembly&gt;<br /> &lt;assemblyIdentity name="Castle.Core" publicKeyToken="407dd0808d44fbdc" culture="neutral" /&gt;<br /> &lt;bindingRedirect oldVersion="0.0.0.0-3.3.0.0" newVersion="3.3.0.0" /&gt;<br /> &lt;/dependentAssembly&gt;</p> <p></p> <p>I did try changing my assembly bindings to 3.3.3.0 with no luck. &nbsp;</p> <p>Thanks</p>
#178174
May 03, 2017 15:47
Vote:
 

Try updating castle.windsor to 3.4

#178178
May 03, 2017 16:05
Vote:
 

Todd, did you find a fix? I'm having the same issue exactly

#186305
Dec 15, 2017 21:14