IoC container for Windows Phone 8.1

Question

I'm currently working on a WP 8.1 app(runtime, not silverlight) and I want to find a IoC container. I'm using Caliburn.Micro, which is great because it's using constructor injection in the view models, but I also have a background agent which can't accces the IoC container from Caliburn.Micro.

In my app, I can do something like this:

...
public MyViewModel(ISyncService syncService, IOtherService otherService)
{
    _syncService = syncService;//and so on for all services
}

Or something like this:

var syncService = IoC.Get<ISyncService>();

In my agent, I can't do the same thing, because Caliburn is of no use there, so I'm forced in doing something like this:

var syncService = new SyncService(new AppSettings(), new AuthenticationService(webClient),
            new PromotionalMessagesService(webClient)...));

I think you get the point. The ISyncService has 7 services required in the constructor, and each service has more in their ctor. The other downside besides ugly code, is that if I change something in the ctor of a service, I have to update it here everytime.

Do you know any good IoC container for WP 8.1 or maybe you have a better idea for this issue?

score 1 · Answer 1 · edited May 23 '17 at 12:17

1

I use SimpleIoc from the MvvmLight Toolkit.

A good How-To can be found here: how to use MVVMLight SimpleIoc?

edited May 23 '17 at 12:17

Community

1
1

answered May 13 '15 at 12:24

Florian Moser

2,583
1
30
40

score 1 · Answer 2 · answered May 13 '15 at 12:37

1

If you look at "Supported .NET versions" table of this page, you'll see that the following DI libraries support WP8.1:

Autofac
Catel
DryOic
Endjin Composition
Grace
HaveBox
IfInjector
LightInject
Mugen
Munq
Ninject
Simple Injector
TinyIoc
Unity

answered May 13 '15 at 12:37

Steven

166,672
24
332
435

Thanks, I didn't knew about this. I think I'll try Autofac and see how it works. – bogdanbujdea May 13 '15 at 13:06

score 0 · Answer 3 · answered May 15 '15 at 02:01

I don't think this is a fault of an IoC container. If a Background Agent is invoked separately to the main app then you may have to configure the required dependencies for that process. In the case of autofac you could reuse modules to register the required dependencies then build the container. These are just rough hand-coded snippets:

var builder = new ContainerBuilder();
builder.RegisterModule<ServicesModule>();
backgroundTaskContainer = builder.Build();

Within the OnInvoke method you might then need to just use an instance scope (http://docs.autofac.org/en/latest/lifetime/instance-scope.html) to isolate the call invocation, or just dispose the container itself when the task is disposed.

protected override void OnInvoke(ScheduledTask task)
{
  using(var scope = backgroundTaskContainer.BeginLifetimeScope())
  {
   var sync = scope.Resolve<SyncService>();
  }
}

IoC container for Windows Phone 8.1

3 Answers3