.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.
On Fri, May 21, 2010 at 4:07 PM, SirDester <mfoc...@tiscalinet.it> wrote: > > Hi all, > I recentrly discovered this fantastic project, and started to use it in > mine. > > I tried to build a single .exe file with all the needed DLLs for my > project, > and I added the log4net.dll to the commandline of ILMerge. All seems to be > fine, the exe is created. > > This project uses a RemoteAppender to log his activities on a remote > machine, who's listening on port 8085. > > If I deploy the "single-exe" file, the RemoteAppender gives me an error > when > trying to connect to the remote Sink. This is the error I receive (on the > client): > > log4net:ERROR [RemotingAppender] Failed in SendBufferCallback > System.Runtime.Remoting.RemotingException - Server encountered an internal > error. For more information, turn on customErrors in the server's .config > file > > and nothing is received from the server. > If I deloy the "not ilmerged" assembly, all goes fine. > > Where am I wrong ? > If you need more info (config files, or other) pelase tell me. > > Thanks in advance. > Maurizio. > -- > View this message in context: > http://old.nabble.com/Log4net-%2B-ILMerge-%2B-RemoteAppender-tp28632939p28632939.html > Sent from the Log4net - Users mailing list archive at Nabble.com. > >
