[LOG4NET-632] UDPAppender does not work when configured by file under .net core

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.0.8
• Component/s: Appenders

Environment

OS Name: Microsoft Windows 10 Enterprise
OS Version: 10.0.17763 N/A Build 17763
OS Manufacturer: Microsoft Corporation
OS Configuration: Member Workstation
OS Build Type: Multiprocessor Free
Hotfix(s): 9 Hotfix(s) Installed.
                           [01]: KB4495590
                           [02]: KB4470788
                           [03]: KB4480056
                           [04]: KB4489907
                           [05]: KB4493478
                           [06]: KB4493510
                           [07]: KB4497932
                           [08]: KB4499728
                           [09]: KB4494441

• Assignee: Unassigned
• Reporter: Keith Henderson
• Created: 30/May/19 21:20
• Updated: 04/Apr/20 22:30

Description

I have run across an issue with the UDP appender where it acts differently depending upon how the system is configured.

 

Attached is 2 sample programs (one zip file). One targets .net 4.7.2 and the other targets .net core 2.1. Each program has 2 methods in it called testByFile and testProgrammatically. Also included in the zip is the log4net.config file I used with both programs.

 

I would expect all 4 methods to behave the same since my programmatic configuration matches the file. When configured by file, the core application does not log to the UDP appender. I have verified this by looking at wireshark while the program is running. The UDP Appender works as expected for the other 3 configuration methods.

 

Obviously the work around is to configure log4net programmatically. My question is why does this one case fail though? I would expect to be able to go to .net core and still use a config file.

 

Any help you can provide would be greatly appreciated.

Keith Henderson