No - it's not a runtime failure - it's a compile time failure. Code Analysis is the culprit - but whilst we've got (allegedly) the same CA installations on both our local dev machines and on our build server the build server ALWAYS gives that failure, even when I can get it building and running successfully locally (with use of SecuritySafeCritical attributes in the appropriate places on my calling code).
I've "fixed" the problem by replacing the LoggingFacility setup with a hand-rolled configuration using the FactoryFacility - but it bothers me that the LoggingFacility is being marked IN SILVERLIGHT as Security Critical. Means that the logging configuration I'm using on my middle tier is subtly different from the client tier (silverlight). On Mar 8, 12:25 pm, Krzysztof Koźmic <[email protected]> wrote: > I'm not an expert on this, I think Hammett will have best idea, but does > that fail at runtime? -- 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.
