New instance per dependency strategy added for type registration

[MKMZ]

@gasparnagy

BoDi currently does not allow to change a strategy of resolving objects. I am currently working on 2 projects that is using SpecFlow with BoDi and I have a problem when I was to have a class with isolated state. It is impossible without the disposal of current ObjectContainer and/or using a different IoC container.

I have added a new strategy which will create a new instance each time Resolve function is executed on ObjectCointainer.

Usage:

container.RegisterTypeAs<SimpleClassWithDefaultCtor, IInterface1>().InstancePerDependency();

var obj1 = (SimpleClassWithDefaultCtor) container.Resolve<IInterface1>();
var obj2 = (SimpleClassWithDefaultCtor) container.Resolve<IInterface1>();
Assert.AreNotSame(obj1, obj2);

[trendfollowerpl]

Please add also usage to RegisterFactporyAs

[MKMZ]

I have also added a strategy for factory registration.

Here is an example:

            container.RegisterFactoryAs<IInterface1>(() => new SimpleClassWithDefaultCtor()).InstancePerDependency();

            var obj1 = (SimpleClassWithDefaultCtor)container.Resolve<IInterface1>();
            var obj2 = (SimpleClassWithDefaultCtor)container.Resolve<IInterface1>();
            Assert.AreNotSame(obj1, obj2);

[gasparnagy]

I quite like this PR. My only concern is about the change in the Resolve method, see below.

[gasparnagy]

The original code was using the already resolved object, the new one, seems to be always resolving a new object. Is this really how this would work? I thought this should decide what to do based on the strategy...

[MKMZ]

I have implemented a stategy in IRegistration implementations (ITypeRegistration and IFactoryRegistration). They are implementing a new interface called IStrategyRegistration which have methods to choose a type of resolving strategy.

Going back to ObjectContainer.Resolve function there was a condition which had tried to resolve an object by looking for a matching instance in resolvedObjects. I had to remove it because the responsibility of resolving a new object should be completely moved to IRegistration classes.

[MKMZ]

This change is not harming any part of library. All unit tests along with a new ones has been passed.

[gasparnagy]

OK. I will check it once more and approve the PR

[MKMZ]

Could you take a look one again at this PR please?

[gasparnagy]

Could you please also add a line about this change to the bodi.cs header (change history)?

[MKMZ]

I have added a line to change history:
"New 'instance per dependency' strategy added for type and factory registrations (by MKMZ)"

[MKMZ]

I have implemented a stategy in IRegistration implementations (ITypeRegistration and IFactoryRegistration). They are implementing a new interface called IStrategyRegistration which have methods to choose a type of resolving strategy.

Going back to ObjectContainer.Resolve function there was a condition which had tried to resolve an object by looking for a matching instance in resolvedObjects. I had to remove it because the responsibility of resolving a new object should be completely moved to IRegistration classes.

[gasparnagy]

This is cool. Sorry for not approving/merging it earlier.