Maintaining LinkDemands across inheritance boundaries

re: Maintaining LinkDemands across inheritance boundaries

Eric Wilson — Tue, 29 Jun 2004 13:40:00 GMT

I don't understand how Full Demands work. In a future blog can you give you a run-down about how they work? In particular, I'm having trouble understanding the "deny" part of Full Demands. Can I demand that my assembly run without full trust, but that the callers code can run however it would like? How do I do that?

re: Maintaining LinkDemands across inheritance boundaries

Peter Torr — Tue, 29 Jun 2004 15:38:00 GMT

The best way to run without FullTrust is to add RequestRefuse declarative attributes to your assembly. See:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconrefusingpermissions.asp

for more information.

A Deny is used to temporarily terminate a stackwalk at the current method.

re: Maintaining LinkDemands across inheritance boundaries

Frank Hileman — Tue, 29 Jun 2004 17:56:00 GMT

Thanks for the excellent explanation. Any chance you could tell us how you got that beautiful colorized text in for the code? I have been frustrated with that part of blogging.

re: Maintaining LinkDemands across inheritance boundaries

Peter Torr — Wed, 30 Jun 2004 03:34:00 GMT

I write my blogs in Word and then use a WordML -> HTML transform and a VSTO project to post to the blog web service.

I really need to upload the final version some day... ;-)

re: Maintaining LinkDemands across inheritance boundaries

Nicole Calinoiu — Thu, 01 Jul 2004 13:37:00 GMT

Peter: Wouldn't making an optional request for non-unrestricted permissions (i.e.: [assembly: PermissionSet(SecurityAction.RequestOptional, Unrestricted=false)]) as per http://msdn.microsoft.com/library/en-us/cpguide/html/cpconpermissionrequests.asp?frame=true be a much simpler means of running without full trust?

As with your earlier comment, most MS recommendations I've seen for refusing full trust go the RequestRefuse route. However, the setup for this is both more tedious and more error-prone, and it doesn't accomodate possible extensions to the available permission sets, so I have to wonder why it seems to be the favoured approach.

Is the RequestRefuse route somehow safer or more reliable? Is there any documentation available comparing the two approaches?

re: Maintaining LinkDemands across inheritance boundaries

Peter Torr — Thu, 01 Jul 2004 22:08:00 GMT

Thanks for the great comment, Nicole.

Please see my follow-up post at http://weblogs.asp.net/ptorr/archive/2004/07/01/170998.aspx