Skip to content

Null reference exception with mono/ninject #121

@bonesoul

Description

@bonesoul

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.

Ninject 4.0 will drop support for .NET < 4.0 (and therefore Mono < 4.0)
support so that we can use concurrent collections. For .NET 3.5 application
we will keep bugfixing Ninject 3.x but not add any new features.

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions