Why leaving StructureMap?
As stated by Jeremy Miller (The guy behind StructureMap): No Silverlight support
Why I need Silverlight support?
I’m starting to write WindowsPhone apps, so looks like I need this.
Purpose of this question?
I love StructureMap. It’s full of features and I’ve been using it for many of my projects. But I have to choose a new one. Which one should I choose?
Other tools?
What I want from new framework?
Supporting Windows Phone.
Right now I’m registering my singleton dependencies using StructureMap like this:
ObjectFactory.Configure(Function(config)
config.For(Of TPlugin).Singleton.Use(Of TConcrete)())
Or this (for generic types):
ObjectFactory.Configure(Function(config)
config.For(Of GetType(IRepository(Of ))).Use(Of GetType(Repository(Of )))())
Or forwarding types:
ObjectFactory.Configure(Sub(config) config.Forward(Of TResolveBy, TRequested)())
I want to do the same things with syntax near to StructureMap(or a better syntax)
What I want from you?
Do you have any experience with them?
Which one do you prefer?
Which one do you recommend to be used in a Windows Phone App?
Any other suggestions?
Update:
What about life cycle and initializing of the concrete type(using a function instead of just defining the type)?
In StructureMap :
config.For(pluginType).Singleton.Use(concreteType)
or
config.For(Of TPlugin).HybridHttpOrThreadLocalScoped.Use(SomeFunction)
I do recommend Ninject. I use it for all my projects mainly because of its auto-binding feature, that allows you to put together interface and its implementation automatically without explicit configuration (like in your samples) – example can be found here.
And you can still use manual configuration just like in your code samples – check out Ninject documentation for examples.
It seems to support Silverlight as well, so it should be usable for you.
EDIT:
As per StriplingWarrior’s comment, the way auto-binding syntax works has changed in recent version of Ninject – check out this SO question for details.