Castle Core version mismatch between binary and nuget

[GoogleCodeExporter]

See https://nuget.org/packages/Autofac.Extras.DynamicProxy2/

Dependencies
Autofac (≥ 3.0.2)
Castle.Core (≥ 3.1.0)

Actually requires Castle.Core ≥ 3.2.0

Original issue reported on code.google.com by tools...@gmail.com on 8 Apr 2013 at 10:55

[GoogleCodeExporter]

Looks like something went wrong during the package build. We have an automatic 
version update script for the .nuspec packages... it must have picked up a 
previous version of Castle.

I think a clean build and package would fix it.

Original comment by travis.illig on 9 Apr 2013 at 12:16

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by travis.illig on 9 Apr 2013 at 12:18

• Added labels: Module-Extras-DynamicProxy2

[GoogleCodeExporter]

When you update a package the previous version is left in the packages folder. 
This is being picked up the task in the build script instead of the newer 
version.

Original comment by alex.meyergleaves on 9 Apr 2013 at 4:46

[GoogleCodeExporter]

I have pushed a 3.0.2 NuGet that should solve the problem.

Original comment by alex.meyergleaves on 9 Apr 2013 at 5:47

• Changed state: Fixed

[GoogleCodeExporter]

Awesome! Thank you

Original comment by tools...@gmail.com on 9 Apr 2013 at 5:56

[GoogleCodeExporter]

I will shortly push an update to the build script that should catch "dirty" 
package folders in the system and let you know so this doesn't happen in the 
future.

Original comment by travis.illig on 9 Apr 2013 at 3:46