Hi, what would be the 3.0 equivalent to this:

Kernel.Scan(x =>
{
    x.BindingGenerators.Add(new
GenericBindingGenerator(typeof(ICommandHandler<>)));

Thanks

Gareth

Generics aren't handled in a special way anymore. Just configure them as you would configure any other class.

From: ninject@googlegroups.com [mailto:ninject@googlegroups.com] On Behalf Of G.McNicol
Sent: Montag, 30. April 2012 15:30
To: ninject@googlegroups.com
Subject: [ninject] Conventions Extension GenericBindingGenerator Equivalent in 3.0

Hi, what would be the 3.0 equivalent to this:

Kernel.Scan(x =>
{
    x.BindingGenerators.Add(new GenericBindingGenerator(typeof(ICommandHandler<>)));

Thanks

Gareth
--
You received this message because you are subscribed to the Google Groups "ninject" group.
To view this discussion on the web visit https://groups.google.com/d/msg/ninject/-/hO5bt0WmEFMJ.
To post to this group, send email to ninject@googlegroups.com<mailto:ninject@googlegroups.com>.
To unsubscribe from this group, send email to ninject+unsubscribe@googlegroups.com<mailto:ninject+unsubscribe@googlegroup s.com>.
For more options, visit this group at http://groups.google.com/group/ninject?hl=en.

So, there's no conventional way to do it?

If not, I'll have to switch containers.

What Remo is saying is that there is no longer any magic special casing of
how generic bindings are handled in the conventions extension vs how types
that are not open generics are handled.

In other words any binding syntax that you can use outside of the
conventions extension will work against it.

Have you looked at the wiki
at https://github.com/ninject/ninject.extensions.conventions/wiki ?

There are examples of how one does bindings in general (though probably not
anything specific re conventions with open generic bindings - the point
being that its just how you'd do it without the conventions)

--R

Gotcha!

Cheers!