All geek questions in one place

Can IoC and the managed AddIn Framework (System.AddIn) work with isolated AppDomains?

If I use the Managed AddIn Framework (System.AddIn) and configure it to use separate AppDomains, can I use the centralized IoC container that is in the main / standard AppDomain app? Can I enable an IoC container through AppDomains?

+3
source share
1 answer

I am going to approach this answer by ignoring part of the MAF equation and focusing on the AppDomain problem. An IoC container could theoretically do what you are describing, assuming that the IoC entry point is inherited from MarshalByRefObject or wrapped in a class, which in turn inherits from MarshalByRefObject. I believe that with a score of 29K + rep, you know this, but:

1) Objects that inherit MarshalByRefObject can be accessed through the borders of the AppDomain using proxying (that is, all calls are sorted by the border of the application to the object).

2) Objects that can be serializable can be transferred across the AppDomain border through serialization, that is, you can get another copy from them in another AppDomain.

IoC AppDomain. -, , -, , IoC, . - if:

1) IoC MarshalByRef

2) , IoC, ( , MBR-).

, IoC, AppDomain, AppDomains. , , MAF, IoC ( IoC).

, IoC ( AOP) API- -, . , IoC - , MBR.

+4

Source: https://habr.com/ru/post/1794132/

More articles:


All Articles