[LOG4NET-379] NullReferenceException in FileAppender when file is not filled.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.11
• Fix Version/s: 1.2.12
• Assignee: Dominik Psenner
• Reporter: David Perfors
• Created: 28/May/13 08:42
• Updated: 28/May/13 11:17
• Resolved: 28/May/13 11:17

Description

When I create a FileAppender without a filename and I call ActivateOptions(), a NullReferenceException is thrown. This is because the filename is first trimmed before the check whether the filename is null or not.