Security rules for subclassing transparent type with safe-critical constructor in Silverlight
In the Silverlight (v4.0) security model, Shawn Farkas says of deriving from types: [...] we see that application types may only derive from other application types or transparent platform types. (*) The * part of this is: (*) This true in 99.9% case. There is another rule about the visibility of the default constructor of a class (which we'll get into next week when we dig deeper into the security model), which also requires that the base class' default constructor (if it has one), must be transparent as well. Practically speaking, you're not generally going to find interesting transparent