Re: declarative and imperative security

From: Marcelo J. Birnbach (mbirnbac@online.microsoft.com)
Date: 02/14/03 

From: "Marcelo J. Birnbach" <mbirnbac@online.microsoft.com>
Date: Fri, 14 Feb 2003 14:26:00 -0800

Declarative security is basically an extension of custom attributes. That
means that you can access them through reflection using GetCustomAttributes.

As always, you have to balances the pros and cons of both options
(declarative and imperative security). For example, if you use declarative
security, is easier for automated tools (like permview) to know what is the
security requirement for the assembly. On the other hand, using imperative
security you can ask for a permission based on some conditional statement.

You can always find good documentation about .net security on
http://msdn.microsoft.com/net/security/

Thanks,
Marcelo

"Doman Maciejko" <doman.is@home.se> wrote in message
news:#Zvm9GB1CHA.2696@TK2MSFTNGP11...
> By using reflection could you use the reflection on declarative code and
by
> doing that invoke private methods? The declarative way of coding security
is
> the only way for the administrator to know how to handle a specific
program.
> If the reflection function could be missused at the same time, which
should
> you prefer, imperativ or declarative way of coding security? Is there any
> way of mixing them together to benefit from both?
>
> Best regard
> Doman
> Sweden
>
>

Relevant Pages