Skip to content

Bizarre dependency requirements #45

@FrederickBrier

Description

@FrederickBrier

I do not mean to be rude, but creating package dependencies like, "Ninject (>= 3.2.0 && < 3.3.0)" for your 3.2.3 release is beyond frustrating. I am trying to use Ninject, Ninject.Extensions.Logging, Ninject.Extensions.Logging.Serilog, Ninject.Extensions.Interception, Ninject.Extensions.Interception.DynamicProxy, Ninject.Extensions.Factory, and Ninject.Extensions.Conventions. My initial project used Ninject 3.3.4, the latest, but a dependency I have yet to identify wanted Ninject 3.3.3. So I downgraded, but all the other Ninject projects with version 3.3.3 or less wanted 3.3.4. Your 3.3.0 wants 3.3.4. Attempting to downgrade Ninject.Extensions.Logging to 3.2.3 results in this narrow window, and so do your other earlier releases. Logging should not be so version dependent. This is DLL hell. Why can't all the Ninject projects just use the same release number and be compatible with each other?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions