Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In an old project I came across the following assembly attribute:
[assembly: SecurityPermissionAttribute(SecurityAction.RequestMinimum, Execution = true)]
I understand that this attribute instructs the clr to not load this dll if the required permissions aren’t available. Is it a good practice to include such declarations in your project as a default?
RequestMinimumhas never been very popular. In fact, most of the Code Access Security model never really gained much traction. Consequently, these areas were greatly reworked for .NET 4.0.As of .NET 4.0, do not use
RequestMinimumbecause it will be ignored.These changes are explained in detail in the documentation for .NET 4.0, http://msdn.microsoft.com/en-us/library/dd233103(VS.100).aspx.