Why can I map my logger names to the loggers that appear in the NT Event Log when I use the NTEventLogAppender?
Unfotunately, the logger names are hardcoded within the message resource DLL (see previous question about NTEventLogAppender), so there isn’t any easy way to override those dynamically… in fact, I don’t think it’s possible to do it, as you’d have to modify the DLL resources for every application. Since most native applications don’t use the Logger column anyway…
Related Questions
- What does the Windows NT Event Viewer complain about missing descriptions for my event messages when I use the NTEventLogAppender?
- What does the Windows NT Event Viewer complain about missing descriptions for my event messages when I use the NTEventLogAppender?
- I am setting up a watch group for an NT event log, and I am ready to define a key. How many of the fields do I need to specify?
- I am setting up a watch group for an NT event log, and I am ready to define a key. How many of the fields do I need to specify?
- LogWatcher won let me scroll to the start of an NT event log, it keeps stopping at a record other than 1 (one). Whats going on?
- Why can I map my logger names to the loggers that appear in the NT Event Log when I use the NTEventLogAppender?
