Sorry if will be saying dumb things here, as I've seen that several years
ago and have no time to review that now; but maybe that'll ring the bell
for somebody
I thought that UserName could be related to user name from principal (thus
basically anything set in code - and can be easily different fo
le value in logs, and if
> it does impersonate,
> then it should be updated. The edge case is multiple applications using
> the same log4net configuration, without impersonation, where the user name
> may change between
> runs but not during the run of the process. Perhaps there