Creating custom CodeAccessSecurityAttribute leads to exception on compile

Question

I'm building a custom CodeAccessSecurityAttribute to handle authorization for my WCF services. I built class A as such:

public class A : CodeAccessSecurityAttribute
{
    public A() : base(SecurityAction.Demand)
    {
        // Constructor Code
    }

    public override IPermission CreatePermission()
    {
        // Permission Creation Code
    }

}

And on compilation it produces this error.

Error emitting 'A' attribute -- 'Serialized security custom attribute is 
truncated or incorrectly formed.'

After playing with it a little I came up with the next sample that does compile without error:

public class B : CodeAccessSecurityAttribute
{
    public B(SecurityAction Action) : base(Action)
    {
        // Constructor Code
    }

    public override IPermission CreatePermission()
    {
        // Permission Creation Code
    }

}

I know it's because the SecurityAction enum isn't directly referenced to public side of Class A, but what I can't figure out is how to make it so that I can do it the Class A method instead of the Class B.

Mormegil · Accepted Answer · 2013-01-15T12:56:26.753

I don’t know the exact reason for the requirement, but the MSDN documentation on CodeAccessSecurityAttribute clearly states

Notes to Inheritors

All permission attributes derived from this class must have only a single constructor that takes a SecurityAction as its only parameter.

Amended: The reason for this requirement is that CodeAccessSecurityAttribute is, from a low-level view, quite different from other custom attributes. Generally, custom attributes are stored in the compiled metadata in the CustomAttribute table. But the security attributes, deriving from SecurityAttribute, are stored separately in the DeclSecurity table. And this table does not contain the general data like the CustomAttribute table, this table contains the value of Action, the name of the attribute type, plus a set of the properties (named arguments) like in the custom attribute case. So, the compiler needs to convert a general custom attribute syntax to an entry in this metadata table, so it needs it to follow the fixed form noted above. (See also this blog post, or Partition II, section 22.11 DeclSecurity : 0x0E of the Common Language Infrastructure (CLI) standard.)

I'll mark this as the answer for now, but what I don't understand is that if I'm forcing the SecurityAction to be one value when calling back down to the base class, why does it care about the instantiating class? — thaBadDawg, Feb 14 '11 at 21:05
@thaBadDawg: The thing is, you might try to add the required parameter to the constructor, but ignoring it and passing a constant to `base()`. However, it seems not to work, anyway, the CAS attributes are not evaluated the “classical” way, it seems. — Mormegil, Feb 14 '11 at 22:42
I'll always be using "Demand". It's annoying that I have to specify it. Oh well, at least it's an enum. — helios456, Mar 22 '12 at 14:10

score 3 · Answer 2 · edited Oct 27 '12 at 21:22

3

If you supply the constructor with a default value you don't have to specify it in the attribute.

public class B : CodeAccessSecurityAttribute 
{ 
    public B(SecurityAction Action = SecurityAction.Demand) : base(Action) 
    { 
        // Constructor Code 
    } 

    public override IPermission CreatePermission() 
    { 
        // Permission Creation Code 
    } 
}

edited Oct 27 '12 at 21:22

Mario S

11,715
24
39
47

answered Mar 28 '12 at 13:00

Terminator

31
1

Creating custom CodeAccessSecurityAttribute leads to exception on compile

2 Answers2

Linked