Thu, 9 Dec 2004 16:03:23 -
>>
>>>Does your client have access to the exception class too? Just a shot in the
>>>dark but with remoting the serialized assemblies have to be available to
>>>both client and server.
>>>
>>>-Original Message-
>>>From:
cess to the exception class too? Just a shot in the
>>dark but with remoting the serialized assemblies have to be available to
>>both client and server.
>>
>>-----Original Message-
>>From: Simon Wallis [mailto:[EMAIL PROTECTED]
>>Sent: 09 December 2004 15:16
&g
Log4NET User"
>Date: Wed, 8 Dec 2004 19:18:17 -
>
>>It looks like the exception is being generated by the remoting server in
>>the ObjectReader.Deserialize methods. This is then being thrown back to
>>the client.
>>
>>How have you setup the remoti
Subject: RE: Error using RemotingAppender: can't find assembly log4net
Now I'm using the example RemotingServer which works perfectly with the
example RemotingClient. It just bombs when I use it with my own client. Here
is the stack trace from DebugView which also shows the configuration of
nerated by the remoting server in
>the ObjectReader.Deserialize methods. This is then being thrown back to
>the client.
>
>How have you setup the remoting server listening on 8085?
>
>Nicko
>
>> -Original Message-
>> From: Simon Wallis [mailto:[EMAIL PROTECTED]
[EMAIL PROTECTED]
> Sent: 08 December 2004 19:08
> To: log4net-user@logging.apache.org
> Subject: Error using RemotingAppender: can't find assembly log4net
>
> Hi, I'm trying to use the RemotingAppender. I got the client
> and server sample code working fine. Now I'm tryin
Hi, I'm trying to use the RemotingAppender. I got the client and server sample
code working fine. Now I'm trying to use the appender in my own code but I'm
getting an error that I can't figure out. When I run my own app (acting as the
client) I see this stack trace in DebugView:
[9596] log4net: