Major Description
I am under the impression that RemotingAppender does register a TcpChannel under the default name 'tcp'. As a result they cannot be used in an application which is itself trying to register a TcpChannel using the default name. Otherwise an Exception will be raised "The channel 'tcp' is already registered".
Of course this can also be solved by changing the application. However this is not always an option.
I would propose changing the TcpChannel name to something like 'log4net', which is unlikely to be used by a third party. I imagine this to be a small change.
