I get this exception at Domain.Build:
This is not practical because we use a plugin structure : some abstract classes are defined in a core assembly, with implementation defined in other assemblies : plugins. With this, I'm required to register plugins even if I'm not using them. Is there is reason for this limitation? |
There is no easy way to handle this issue without this workaround, i.e. we decided to choose the less dangerous among two evils:
This is a quickfix, so we'll think about full solution. But for now we can't offer anything better. I understand : please let me know when this is fixed, it's not really practical. The issue is fixed. |
Hello,
It seems that abstract type are being inspected this way according to the following issue. I'll investigate the reason of its implementation soon.