PrincipalPermission Attribute in Data Access, formerly OpenAccess ORM General Discussions

Josh

12 posts

Member since:
Aug 2008

Posted 31 May 2009 Link to this post

Is it possible to use additional attributes such as PrincipalPermission on the partial classes generated by the reverse mapping tool? I was playing around with this and I was not seeing the effect I expected. After a little research, I saw this in my build log

    
            warning : Some attributes are removed from the nested type 'ppiatm.QAReporter.Data.InspectionReport'. 

            Attributes before enhancement: AutoLayout, AnsiClass, Class, Public, HasSecurity, BeforeFieldInit.

             Attributes after enhancement: AutoLayout, AnsiClass, Class, Public, 

            BeforeFieldInit [class=ppiatm.QAReporter.Data.InspectionReport]

Is this the complete list of attributes being removed or would it also be removing the PrincipalPermission attribute?

Jan Blessenohl

Admin

707 posts

Posted 03 Jun 2009 Link to this post

Hi Jim,
The removed HasSecurity attribute is your PrincipalPermission attribute. The emit API is not able to write the attribute because it is counted as non runtime attribute. This causes the removal. Which attribute are you really specifying on the type?

Kind regards,
Jan Blessenohl
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.