Thanks for looking at this Krysztof As I said, the error only surfaces on our build server with its particular configuration of Code Analysis, and NOT on our dev machines which have (allegedly) the same configuration - and the work-around has solved the problem pro-tem.
Removing the attribute for the Silverlight build would seem to be the sensible option if there's no Security Critical aspect to the code in that build configuration. I'll let you know if we work out what (if any) the differences in build configuration are. -- You received this message because you are subscribed to the Google Groups "Castle Project Users" 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-users?hl=en.
