Geek Answers Handbook

Does Dynamo IoC work with MonoTouch and MonoDroid?

I am curious from any possible inversion of C # .NET management solutions there if anyone has ever tried Dynamo IoC ( http://www.dynamoioc.com/ ) and does it work with projects designed for MonoTouch and MonoDroid?

Until I explicitly use MonoTouch or MonoDroid, I use Unity 3D ( http://www.unity3d.com ). I expect that if IoC infrastructure (like Dynamo) runs on MonoTouch and MonoDroid, it will likely satisfy my needs with Unity 3D.

NOTE. I conducted research on the inversion of management containers and their compatibility with MonoTouch, MonoDroid, etc. within a few days; these questions arise not from laziness, but from the lack of details that I discovered during my research, in particular regarding Dynamo IOC and its compatibility with MonoTouch, MonoDroid, etc.

+7
source share
3 answers

I can not answer the question about DynamoIoC, but I used TinyIoC and OpenNetCF IoC on MonoTouch and MonoDroid without any problems.

In MvvmCross, I currently use a very limited set of OpenNetCF functions and work through wp7, ios, droid and winrt.

+5
source

Dynamo cannot be used for C # projects targeting iOS platforms through MonoTouch or Unity 3D.

I was able to find this regarding Mono limitations, kindly provided a few other questions and answers here in StackOverflow; after a more thorough analysis of Dynamo IoC code and a better understanding of what is meant by the System.Linq.Expressions namespace, it seems that Dynamo can achieve most of its speed by using the dynamic expressions provided by Linq. I understand that code using System.Linq.Expressions falls into the same category as dynamic code generation, which makes Dynamo IoC unsuitable for MonoTouch (as well as using Unity 3D proxy projects focused on iOS).

+1
source

I'm just getting started with the MonoTouch project, and I'm using Munq.IocContainer . Munq is a small DI infrastructure that I used earlier in the ASP.NET MVC project and Windows Mobile 6. Although it does not have bells and whistles of large frames, it is quick and easy to configure.

Please ignore the above. I started using Munq, which worked very well in the simulator, but failed when I tried to deploy a real iPhone. This is because Munq JIT is some code that AFAIK is not ok in MonoTouch on iOS. I returned to Funq , from which Munq is derived. Munq was actually intended for use in ASP.NET MVC3, so going back to Funq also means that there are no system.web links that need to be removed.

0
source

More articles:


All Articles