Thanks for your kind and fast answer. Based on what you anwsered, I decided to try another way to remote log my activities, and I gave a shot to UDPAppender, that doesn't require remoting... I implemented that solution, and all is fine now, I can ILMerge the log4net.dll without any problem.
I understand that it's best not to create single exe and use GAC, but what I needed was a little .exe to execute with psexec on remote machine whitout having the problem to deploy it before execution "manually", leaving to psexec the weight of all actions (copy, execute, delete file). For now, thanks for your explanation on remoting. Bye. Maurizio. Yuriy Taraday wrote: > > .Net Remoting identifies type by its *full* name with *full* name of > containing assembly. > So if you use separate dll, remoting happens throw interface > "log4net.Appender.RemotingAppender.IRemoteLoggingSink, log4net, > version=1.2.10.0, PublicKeyToken=....". > When you use single-exe thing, your end of remoting cannot understand > where > to get this interface because it only has smth > like "log4net.Appender.RemotingAppender.IRemoteLoggingSink, mybigexe, > version=...., PublicKeyToken=....". > Good solution is never use single-exe but use GAC as much as you can. > -- View this message in context: http://old.nabble.com/Log4net-%2B-ILMerge-%2B-RemoteAppender-tp28632939p28634654.html Sent from the Log4net - Users mailing list archive at Nabble.com.
