I didn't think so. Must have some stale references somewhere. thanks
On Feb 17, 1:56 pm, hammett <[email protected]> wrote: > 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. > > > > > > > > > > On Fri, Feb 17, 2012 at 6:33 AM, cneuwirt <[email protected]> wrote: > > 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 > > > -- > > 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 [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group > > athttp://groups.google.com/group/castle-project-devel?hl=en. > > -- > Cheers, > hammetthttp://hammett.castleproject.org/ -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
