I'll add a few more details. I've checked that all the deployed DLLs are identical versions between the WCF service and the ASP.NET app. The version numbers for all castle DLLs and log4net match.
I'm using the 1.2.10 version of log4net with the 1b44e1d426115821 key. My WCF service and ASP.NET MVC app are separate IIS applications but exist in the same app pool, if that matters. The app pool runs under credentials that have access to the log table in the DB (obviously it has access since the WCF app can, at least, partially log). What seems odd to me is that Castle is clearly populating the ILogger properties with loggers. They're just not all working. It's also rather odd that it works for some classes and not others inside the WCF service. -- You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/castle-project-users/-/5PZIDi4xvLkJ. 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.
