I have a large project were my team is using convention based registration to handle the majority of the work. We then re-register a handful of types so we can handle changing lifetime manager and other details about the registration. This second registration of the type does not clear the interception behaviors which causes the behavior to be in the pipeline twice. As a workaround we are finding the IInterceptionBehaviorsPolicy for any type that needs to be re-registered and removing it before re-registering.
@Minx-SigEp wrote:
I have a large project were my team is using convention based registration to handle the majority of the work. We then re-register a handful of types so we can handle changing lifetime manager and other details about the registration. This second registration of the type does not clear the interception behaviors which causes the behavior to be in the pipeline twice. As a workaround we are finding the IInterceptionBehaviorsPolicy for any type that needs to be re-registered and removing it before re-registering.
I have created a sample project that shows the issue as well as a screen shot. The sample project can be found at https://github.com/Minx-SigEp/UnityInterceptionBug