c# - Abstract base classes and appdomains -


If I do not understand my next explanation enough then I apologize; I know it again, though I try to do otherwise.

I am writing a service that uses user-defined plugins. I am trying to isolate them - using the defined interface in a shared assembly - keeping their organizations out of the service's appdomain.

What I want to kill is abstract functionality of the base classes which will be normal for all the implementations of the interface, so the intrinsic basic classes mean that if any abstract is in the service service assembly, Those who meet this sub-class, they are dragged to their sovereigns in the servicedom of the service. However, there are internal members in the basic basis (properties with internal sets and public gates) that use the service, so it should be in the same assembly, which may be possible.

It seems as if I want it is not possible, but I also believe that this is because I am taking a wrong view. I have learned the method of good patterns and practices in other ways. I'm trying hard to get better use.

"post-text" itemprop = "text">

Do you want an interface with an abstract base class to apply the interface and that the derivative classes can get them. In this case, you can maintain your separation with the interface, but you can still provide an abstract base class for implementation. It also has the advantage that the intangible base class is optional.


Comments

Popular posts from this blog

c# - How to capture HTTP packet with SharpPcap -

php - Multiple Select with Explode: only returns the word "Array" -

php - jQuery AJAX Post not working -