Working with Windsor trunk security changes

13 views
Skip to first unread message

cneuwirt

unread,
Feb 17, 2012, 9:33:55 AM2/17/12
to Castle Project Development List
The latest trunk of windsor contains the following assembly security
related attribute
[assembly: System.Security.AllowPartiallyTrustedCallers]
[assembly:
System.Security.SecurityRules(System.Security.SecurityRuleSet.Level2)]

When referencing windsor assembly with these attributes included, I
get strange MemberAccess exceptions (when calling default ctors). Are
assemblies referencing Windsor now required to included security
attributes in their assembly? If so, which ones?

thanks,
craig

hammett

unread,
Feb 17, 2012, 2:56:10 PM2/17/12
to castle-pro...@googlegroups.com
Not at all. This is not a viral setting.

I've seen similar exceptions, but they went away with a clean build.
Make sure you dont have any assembly that referenced an older version
of Windsor.

> --
> You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
> To post to this group, send email to castle-pro...@googlegroups.com.
> To unsubscribe from this group, send email to castle-project-d...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
>

--
Cheers,
hammett
http://hammett.castleproject.org/

cneuwirt

unread,
Feb 17, 2012, 2:58:23 PM2/17/12
to Castle Project Development List
I didn't think so. Must have some stale references somewhere.

thanks

hammett

unread,
Feb 21, 2012, 6:23:48 PM2/21/12
to castle-pro...@googlegroups.com
Did that work?

Craig Neuwirt

unread,
Feb 22, 2012, 8:07:41 AM2/22/12
to castle-pro...@googlegroups.com
I believe it will. I haven't verified it completely since I need to rebuild several libs that reference the old windsor.
I'll certainly let you know if I have any issues.

thanks

Reply all
Reply to author
Forward
0 new messages