Explicit interface implementations

Feb 10, 2011 at 9:42 PM

I've been running the Code Analysis tool on my project (aka FxCop) and noticed a few warnings coming up in the Framework classes.

There's a few Dispose-related ones that I might submit a patch for, but some I'm curious about are like this:

C:\dev\CaliburnMicroFork\src\Caliburn.Micro.Silverlight\Parameter.cs(40): warning : CA1033 : Microsoft.Design : Make 'Parameter' sealed (a breaking change if this class has previously shipped), implement the method non-explicitly, or implement a new method that exposes the functionality of 'IAttachedObject.AssociatedObject.get()' and is visible to derived classes.

Just wondering if there was a reason for using the explicit implementation? If there is, that's good, if not I might update those in a patch too.