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

Bizarre dependency requirements #45

Open
FrederickBrier opened this issue Jun 12, 2019 · 0 comments
Open

Bizarre dependency requirements #45

FrederickBrier opened this issue Jun 12, 2019 · 0 comments

Comments

@FrederickBrier
Copy link

FrederickBrier commented Jun 12, 2019

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?

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

No branches or pull requests

1 participant