Have you considered using @GrumpyDev 's TinyIOC


Grumpy dev released his public version of TinyIOC which might be better to use for IOC

Closed May 17, 2013 at 5:32 PM by Mister_Goodcat


Mister_Goodcat wrote Apr 21, 2013 at 10:04 AM

Hi and thanks for the suggestion. Even though I looked at all sorts of existing solutions that could be used instead of reinventing the wheel, Liphofra tried to solve problems without depending on any external projects by the time it was created (something that actually was caused by specific requirements from its non-public phase and use in previous projects). One issue with TinyIoC (which in my eyes isn't so tiny btw. :)) was the unclear licensing. I just learned that there was a license statement all the time somewhere hidden in the sources and that it will be made clearer in the future by placing it more prominently (see https://github.com/grumpydev/TinyIoC/issues/32, for example) - so it might actually be something to consider for the future.

Thanks again,

Mister_Goodcat wrote May 17, 2013 at 5:30 PM

I actually tried to write a sample how to use TinyIoc with Liphofra, which in my eyes shouldn't be hard to do: Liphofra is designed to exchange the built-in types for others, as long as you write a small adapter to satisfy the required interfaces.

However, after playing around with TinyIoc for a bit I decided not to finish it. The current version doesn't even compile when you pull it into a new Windows Phone project; that issue has been reported more than a year ago and people have submitted pull requests for it in the same timeframe - however the problem persists. It's not that the problems would be hard to fix, but that and other issues in the phone code path (e.g. around the ReaderWriterLockSlim code) do not shed the best light on the project with regards to Windows Phone.

However, still thanks for your suggestion. I should indeed provide better guidance on how to plug in alternative implementations for the built-in features.

wrote May 17, 2013 at 5:32 PM