I have created a server that has an object that can be referenced via
remoting.  When I reference the object from the client, everything works
just fine until I shut down the server.  Once the server is shut down, and
at the exact moment it stops listening on its port, the client ...

Problem:
I am serializing an object to the client, no problems
there.  However, during parts of the object's execution
the object needs to know if it is running on the client or

I want to copy a file from Server to Client . I am using .net remoting. I
want to copy a .mdb file from server machine to local client machine. How
can it possible .
Thanks .

I've got a slight problem - does anyone have any
suggestions?
I have a server with a few potentially long-lived clients.
Each client maintains a large number of long-term

All-
I've found a few .net remoting examples online (and in msdn), but they all
use console apps as their example where they start the server part on the
server in a console and then run the client.

I cannot get any remoting examples to work across a network (LAN
intranet).  If I use TCP, I keep getting "Requested service not found"
error whenever accessing a method or property on the remote object.
When I switch it to a HTTP on an IIS virtual directory, I keep getting

My singleton server object has a method that creates and
returns a big dataset to a client application.
Although the server doesn't have any reference to dataset
after returned it, the server memory grows and doesn't

I thought I could just return an XmlDocument from my
Remote Server but I am getting an "Internal Server Error"
message.  I think the code is good.  The only thing I can
come up with is maybe XmlDocuments are not serializable.  

Why is Remoting better than Sockets ?

Does anybody have a simple Remoting calback sample?. Thanks.

I'm new to remoting.  I have written a remotable object
that makes use of a business object.  What I have found is
that I need to copy both the remotable object along with
the business component out to the client in order for

I've noticed something interesting: if I configure a
remoting server in code like
HttpChannel Channel = new HttpChannel(8088);
ChannelServices.RegisterChannel(Channel);

I heard from my boss:
That .Net Remoting is not a recommended solution for any environment that is
not high speed LAN.
In other words, that any recommended remote communication for slow wan,

Basically my situation is this, I have a server implemented in C++,
unmanaged code, using proprietery protocol over TCP/IP to communicate
with the cilent(c++ also).
Now, I am implementing the another client in C#. Server side can not

Is there any way to do remoting and pass a type that is defined separately
(but identically) in both the server and the client instead of having to
have them share a dll between them?
Thanks,