> You don't need to maintain your own version of log4net. You have written a > custom appender, based on the EventLogAppender. All you need to do is include > your appender in your own assemblies somewhere and then specify the assembly > qualified type name for the appender in the configuration.
That's true enough...I might have more success with that argumentative approach. :-) Anyhow, I thought that I'd post about getting the actual adapter to support categories, since it seemed like a simple oversight. Please don't think that I'm trying to get you to do my work for me. :-D > Is setting the category to a single fixed value for all the messages logged > ok? Or should the value be set on a per event basis? For my purposes at least, yes...I'm not sure how other log4net users might want to use categories. Here, other deliverables are using the category to indicate what service is doing the logging, so in order to mimic that with log4net in my services, I was planning on giving each service its own appender with the category set as a property on the appender. So, I personally don't need to make the category a LoggingEvent property as is done with the event ID, nor extend the logging interface as done in log4net.Ext.EventID as Ron suggested. However, were you to add category support to log4net, I'm not sure which would be the more generally useful approach. Thanks for your replies, Javan Gargus Software Developer, GE Fanuc [EMAIL PROTECTED]
