Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Castle.Core versioning problem #228

Closed
StevenBonePgh opened this issue Jan 13, 2018 · 1 comment
Closed

Castle.Core versioning problem #228

StevenBonePgh opened this issue Jan 13, 2018 · 1 comment

Comments

@StevenBonePgh
Copy link
Contributor

Hello Elad,
I've had the need to update some dependencies and I'm having an issue with Castle.Core - the version referenced by WampSharp has an assembly version of 4.1.1.0, and it looks like they changed the assembly version to 4.0.0.0 in the latest 4.2.1 (or likely 4.2.0) nuget package. That results in the need to do the following:

<bindingRedirect oldVersion="0.0.0.0-4.1.1.0" newVersion="4.0.0.0" />

Which I don't really want to do. Could you please update WampSharp to use 4.2.1, which is apparently their go-forward versioning strategy? Moq and others have also released versions to coincide with their change. Reference this (and other) discussions: #288 Castle.Core

Thanks, as always!

@darkl
Copy link
Member

darkl commented Jan 13, 2018

Done (v1.2.7.47-beta).

Elad

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants