Bernd,
In case you haven't yet found it, the documentation for the rule is at
http://www.gotdotnet.com/team/fxcop/Docs/Rules/SecurityRules/PartialTrustTypes.html. That said, it makes no sense to add an inheritance demand to your sealed
class. The FxCop engine is probably not assessing the sealed condition wrt
this rule, which most likely why you're still get the rule violation even
after adding the link demand. If your code protects against the risks
presented by the related partially trusted methods issue
(
http://www.gotdotnet.com/team/fxcop/Docs/Rules/SecurityRules/PartialTrustMethods.html),
you've very likely done enough to exclude this violation.
If you're still worried, it might be worth posting to the FxCop message
board at
http://www.gotdotnet.com/community/messageboard/MessageBoard.aspx?ID=234. HTH,
Nicole
[quoted text, click to view] "Bernd Helzer" <bhelzer@byu.net> wrote in message
news:eb0CQ8WsEHA.1404@TK2MSFTNGP11.phx.gbl...
>I keep getting an error in FxCop: Partially trusted types extend only other
>partially trusted types
> Nothing I do seem to make the error go away.
> My assembly AllowsPartialTrustedCallers, but during Design time it's fine
> to require FullTrust.
> My original declaration looked like this:
>
> public sealed class Designer : ControlDesigner
> After some investigation I decided what I really wanted was:
>
> [PermissionSetAttribute(SecurityAction.LinkDemand, Name="FullTrust")]
>
> public sealed class Designer : ControlDesigner
>
> but that doesn't seem to make a difference in FxCop.
> Am I doing something wrong or is this a problem in the rule?
>
> Bernd
>
>
>
>