|

»

Working with Windsor trunk security changes

View: New views

5 Messages — Rating Filter: Alert me

	Working with Windsor trunk security changes by Craig Neuwirt :: Rate this Message: \| View Threaded \| Show Only this Message 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 castle-project-devel@.... To unsubscribe from this group, send email to castle-project-devel+unsubscribe@.... For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
	Re: Working with Windsor trunk security changes by hammett-2 :: Rate this Message: \| View Threaded \| Show Only this Message 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 <cneuwirt@...> 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 castle-project-devel@.... > To unsubscribe from this group, send email to castle-project-devel+unsubscribe@.... > For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en. > -- Cheers, hammett http://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 castle-project-devel@.... To unsubscribe from this group, send email to castle-project-devel+unsubscribe@.... For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
	Re: Working with Windsor trunk security changes by Craig Neuwirt :: Rate this Message: \| View Threaded \| Show Only this Message I didn't think so. Must have some stale references somewhere. thanks On Feb 17, 1:56 pm, hammett <hamm...@...> 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 <cneuw...@...> 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 castle-project-devel@.... > > To unsubscribe from this group, send email to castle-project-devel+unsubscribe@.... > > 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 castle-project-devel@.... To unsubscribe from this group, send email to castle-project-devel+unsubscribe@.... For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
	Re: Working with Windsor trunk security changes by hammett-2 :: Rate this Message: \| View Threaded \| Show Only this Message Did that work? On Fri, Feb 17, 2012 at 11:58 AM, cneuwirt <cneuwirt@...> wrote: > I didn't think so. Must have some stale references somewhere. > > thanks > > On Feb 17, 1:56 pm, hammett <hamm...@...> 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 <cneuw...@...> 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 castle-project-devel@.... >> > To unsubscribe from this group, send email to castle-project-devel+unsubscribe@.... >> > 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 castle-project-devel@.... > To unsubscribe from this group, send email to castle-project-devel+unsubscribe@.... > For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en. > -- Cheers, hammett http://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 castle-project-devel@.... To unsubscribe from this group, send email to castle-project-devel+unsubscribe@.... For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
	Re: Working with Windsor trunk security changes by Craig Neuwirt :: Rate this Message: \| View Threaded \| Show Only this Message 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 On Feb 21, 2012, at 5:23 PM, hammett wrote: > Did that work? > > On Fri, Feb 17, 2012 at 11:58 AM, cneuwirt <cneuwirt@...> wrote: >> I didn't think so. Must have some stale references somewhere. >> >> thanks >> >> On Feb 17, 1:56 pm, hammett <hamm...@...> 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 <cneuw...@...> 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 castle-project-devel@.... >>>> To unsubscribe from this group, send email to castle-project-devel+unsubscribe@.... >>>> 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 castle-project-devel@.... >> To unsubscribe from this group, send email to castle-project-devel+unsubscribe@.... >> For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en. >> > > > > -- > Cheers, > hammett > http://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 castle-project-devel@.... > To unsubscribe from this group, send email to castle-project-devel+unsubscribe@.... > For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en. > -- 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-project-devel@.... To unsubscribe from this group, send email to castle-project-devel+unsubscribe@.... For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.