-
Notifications
You must be signed in to change notification settings - Fork 494
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
Null reference exception with mono/ninject #121
Comments
may be we should consider other ioc frameworks; |
https://simpleinjector.codeplex.com/ but seem to support mono. tinyioc seem to support named instances. let's the carry the discussion over here instead of irc, as it's hard to follow. |
and here is the cryptic message from ninject/mono - i guess none of us want to deal with users reporting cryptic exception caused by ninject -- and again we mainly target mono. So our build process for mono should be flawless. we have to move to tinyioc or the other i guess.
|
Fixed with: #128 |
seems we have to use ninject for mono - download page lists the build-server;
but the thing how we'll get this automated?
as we are building a server application we mainly target mono + linux - and without getting this automated, ninject will just harm.
more interestingly;
ninject/Ninject#126
they're dropping support for mono - which is quite something I'm not happy with.
and again i'm quite not happy with cryptic errors & exceptions of ninject which made me consider getting it out of the project and instead implement our own dependency injection pattern -- yes we can't have the nifty feature of ninject -- but if we follow our current pattern with a few resolvers we can handle the job i guess..
I vote for the DI pattern for sure but usability should be our main priotry. Wanted to hear you guys opinions.
The text was updated successfully, but these errors were encountered: