Hi, > You can use two different implementations to provide the CLS and non-CLS > compliant versions, with the non-CLS version subclassing the CLS one. You > can have as many LogImpls side-by-side as you like.
Wouldn't it be nice to extend log4net so that it e.g. provides an IClsLog that is CLS compliant and the ILog that adds all non-CLS compliant methods to IClsLog? I will do this locally, but this is in my opinion something that might also be useful for other people to have. >> People who need the user identity in their log message could >> add it as a context property. Like this, you could avoid the >> negative impact on those who don't need it. > > The WindowsIdentity.GetCurrent is only generated on demand. i.e. when > using the %w or %username patterns in the PatternLayout. It is also I didn't know that. In that case, that's no problem :-) Thank you and a nice weekend to all, Andy
