Changes to the Logging Application Block

The following changes have been made to this version of the Logging Application Block:

• Fixed : The WMI provider for several trace listeners now supports saving changes. WMI settings are added to support saving changes for FormattedEventLogTraceListener and FormattedDatabaseTraceListener.
• Fixed : WMI support for trace listeners can now save the new Filter property to configuration objects. Logging Application Block files are updated so they can save a Filter value when pushed from WMI. WMI settings are added to support saving changes for FormattedEventLogTraceListener and FormattedDatabaseTraceListener.
• Fixed : The Database trace listener no longer fails if no formatter is specified. The assembler for the FormattedDatabaseTraceListener now uses the inherited GetFormatter method, which determines whether a new formatter should be created.
• Fixed : Running the logging Unity integration now works on release mode.
• Added: Configuration support to opt-out of the impersonation-reverting default setting has been added. This fixes the rolling flat file trace listener problem when used in a Web application and when impersonation is enabled. To opt-out of the impersonation-reverting default mode, set the new <section> revertImpersonation attribute to false. The default setting is true. This supports configuration support, design time support, and manageability support (both WMI and group policy).
• Fixed: Log entries with a user supplied categories collection that result in a non-serializable object is fixed. The potentially non-serializable categories collection is now copied to an array before serializing.
• Fixed : The XmlLogFormatter now properly generates an XML representation of an object when that representation may contain characters that should be escaped. The XmlLogFormatter now uses an XmlWriter instead of a StringBuilder.
• Fixed : FormattedTraceListenerWrapperBase now checks its filter before it forwards requests to the wrapped trace listener.
• Fixed : The rolling file trace listener no longer fails when rolling for size only and the date template is empty. The log file is not truncated when the size threshold is reached. A timestamp pattern is not necessary or desired when using an increment because the increment is appended to the base file name.
• F ixed : The constructor overloads for FormattedTextWriterTraceListener now use the formatter properly.
• Fixed : A file name error is fixed so that the file name is now correct, fileNameWithoutExtension + .20080815.1" + extension, when the datetimepattern is set to yyyymmdd or yyyyddmm format in the rollingflatfiletracelistener.

Changes to the Exception Handling Application Block

The following changes have been made to this version of the Exception Handling Application Block:

• Changed : When building a LoggingExceptionHandler, instead of creating a logging stack every time and ignoring it if the value for the use the default logger flag on the handler is set to true, the build process now uses the value for the flag in the configuration file to create the handler with either Logging.Writer (if true) or the result of creating a new stack (if false). The handler now only knows it has a writer; it does not know where it came from.
• Fixed : The DesignTime nodes for ExceptionHandlers are now handled correctly when using template-based messages. The variables are now accessed correctly when mapping an exception handler configuration object to the corresponding node and a valid configuration is saved.
• Fixed : Invalid XML generated by the XmlExceptionFormatter is fixed. Exception formatters now must include the HandlingInstanceId (which is generated on each exception handling request). The way the exception formatter includes HandlingInstanceId depends on the individual formatter. The XmlExceptionFormatter adds it as an attribute of the top-level Exception element; the TextFormatter adds it as the first line of text. An ID equal to Guid.Empty can be ignored.

  The logging exception handler no longer adds the exception handling ID to the message to log. The formatter handles the ID. Exception Formatter types used with the logging exception handler must now implement a constructor with the parameters TextWriter, Exception, and Guid.

  There is no backward compatibility support. Creators of custom formatters must update the formatters to be used with this version so that the handling instance ID is not lost because a formatter does not support it.