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

Is Ninject Maintained or not? #384

Open
aqibbanday opened this issue Sep 14, 2021 · 11 comments
Open

Is Ninject Maintained or not? #384

aqibbanday opened this issue Sep 14, 2021 · 11 comments

Comments

@aqibbanday
Copy link

No description provided.

@NoskovEugene
Copy link

I think no, because I ask a question one year ago, and they still not answered

@dadhi
Copy link

dadhi commented Sep 22, 2021

@aqibbanday @NoskovEugene Are you using it in the old code base or with the new MS.DI abstractions?

@aqibbanday
Copy link
Author

I am using it with .NET 5.

@dadhi
Copy link

dadhi commented Sep 22, 2021

@aqibbanday Sorry for the survey:

  • Are you using Ninject for the specific feature(features)?
  • How big is the usage scope, e.g. 100 registrations or 1000 or more?

@aqibbanday
Copy link
Author

Less than 50.

@aqibbanday
Copy link
Author

I am using ninject for DI and no other library.

@dadhi
Copy link

dadhi commented Sep 22, 2021

Thank you.

I am using ninject for DI and no other library.

I mean, what is the specific Ninject feature(s) you love and which is keeping you on Ninject wagon,
comparing to the Microsoft.DependencyInjection or others?

Or are you using Ninject for the other reasons?

@aqibbanday
Copy link
Author

Nothing is keeping me on Ninject,if this library is not maintained I am planning to move to some other library probably Microsoft dependency injection

@NoskovEugene
Copy link

@dadhi, i love ninject because it can dynamic resolve dependencies

@dadhi
Copy link

dadhi commented Sep 27, 2021

@NoskovEugene

love ninject because it can dynamic resolve dependencies

What is that? Could you provide the example?

@rychlym
Copy link

rychlym commented Feb 12, 2024

I have recently spot one NInject feature allowing setup custom NLog Logger (with the correct name parameter) resolution
( https://stackoverflow.com/questions/13748455/ninject-logger-using-nlog/65797518#65797518 )

_kernel.Bind().ToMethod(p => LogManager.GetLogger(p.Request.Target?.Member.DeclaringType.FullName ?? typeof(App).GetType().FullName))
As I understand, In detail, It allows to get the to the service type via the "p.Request.Target?.Member.DeclaringType path". This allows me to register services without need of explicit expression of arguments (because in case of a custom NLog logger is good to manually specify the way how to instantiate the logger based on the service type name.) Microsoft DI container does not have such a functionality and I haven't found a way if possible to extend it (if so please let me know :) )

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

4 participants