Problem with implementing Interceptor template

I am trying to develop an Interceptor infrastructure (in C #) where I can simply implement some interfaces and with some static initialization register all my interceptors using a common dispatcher that will be called later.

The problem is that my Interceptor implementations never reference my application, so static constructors are never called, and as a result, hooks are never registered.

If possible, I would like to leave all the links to my Interceptor libraries from my application, as this is my way (hopefully) to provide a forced connection between the various modules.

Hope this makes sense. Let me know if I can clarify ...

Does anyone have any ideas, or perhaps a better way to implement my Interceptor template?

Update: I came across Spring.NET. I had heard about this before, but never looked at him. It looks like it has a lot of great features that would be very useful for what I'm trying to do. Does anyone have any experience with Spring.NET?

Tia,
Jeremy

+3
source share
2 answers

ASP.NET .NET, , , , . , , , ().

: http://www.sharpcrafters.com/aop.net

0

Spring.NET, Unity Framework StructureMap - , , . MVC factory . , NinJect, - XML (Ninject API). , , , .

IOC, , XML, , , , () . , .

0

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


All Articles