Potential contention in PipelineManager using methodToken?

Mar 1, 2010 at 9:51 PM

I've been having a problem where some of my CallHandlers are not being called and the method is directly called without going through the Handlers. After a bit of debugging, I discovered that the method token used in PipelineManager was the same for my Validate as it was for another method in the base class on a property setter, in my case get_RaisePropertyChanged. Because I don't have any handlers on my property setter, the SetPipeline was overwriting my existing methods pipeline with one that was empty, causing the handlers to not execute. I was able to fix that particular issue by sealing that property, but now, I've found another instance of it, is this a known issue or is there a common workaround?

Mar 2, 2010 at 4:50 AM

Known issue and has been fixed in Unity 2.0.