Skip to content

Castle.Core versioning problem #228

@StevenBonePgh

Description

@StevenBonePgh

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!

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions