I'm just getting started with a Remoting application.  My plan is to
host the 'server' portion inside a Windows Service.  The client side
will be (for the most part) an ASP.NET application that has
impersonation enabled.  I want to use a TCPChannel instead of an HTTP

I have 2 applications running on my desktop. App1 wants to
activate App2 and call a public method in the mdi main
form, passing this method 2 pieces of info: one string,
and one integer.

My problem is that I can't restart my remoting server. This is how I
start the server:
m_ServerSinkProvider = new BinaryServerFormatterSinkProvider();
m_ServerSinkProvider.TypeFilterLevel = TypeFilterLevel.Full;

This message is a variation on my recent "Connecting to a Windows
service" post.  In that post, I asked if a client on a PocketPC can use
remoting to connect to a Windows service on a server.  It was pointed
out that the Compact Framework does not support remoting, which

I am doing some tests re. serialization performance.
Server and client are different machines, 100 mbs ethernet).
Both machines quite slow, specially the server (server ~ 600 MHz, client ~
1.4 GHz)

What am I doing wrong? Any help you can provide will be greatly appreciated!
I have the following class defined in a shared object assembly.
   public class RMInfoMessageEventWrapper : MarshalByRefObject {
       private RMInfoMessageEventHandler callback;

I am designing a case labeling application in which a controlling
application will receive weights from a scale and send them to a label
printer.  Because the production floor is cold and wet, we want to have the
computer running this application in a separate room, talking to the ...

I would like to know what the 'official' method of communication
between a windows service (*not* a web service) and an application is.
To be more specific: I am writing a windows service with .NET that is
used for backuping purposes. The user should for example be able to

Here is a problem. I can load assembly and create class
from assembly. But, when I'm done with it, I can not free
DLL. Even if I'm not using any classes from this assmbly
anymore, even if I force GC.Collect(), DLL is still

I have a remote object containg two classes ,one marked as seriazable and
the other one has inherited MarshalByRefObject.I have my own host programme
which loads remote object on the server .On the client when I work with the
class which has inherited MarshalByRefObject,there is no ...

When I compile my project for Release there are 2 folders that get
created called temp and TempPE. What are these folders?
SK

Is there a way for the server (the MBR object) to observe the
lifetime of the client, meaning that if the client for some reason
is no longer available, the server can be aware of it?
This is an opposite situation than most of the remoting

Hi there, I've just encountered a weird problem making a remoted
component, and I'd like to know is someone of you can explain it.
I've created two assemblies (DLLs), one containing a simple interface
(one method, int parameters and int return value) and the other one

I got a really bad headache with this exception. I have a class named
THECLASS which implements two static methods to provide externalization of
the object itself. One method is LOAD from file (deserializing) and the other
one is SAVE to file (Serializing). This class is in a DLL ...

I am working on a large project that is being converted from VB6 to .NET. We
have been benchmarking performance differences between ADO Recordsets via
DCOM and DataSets via remoting (TCPChannel), and so far we are completely
stunned at how poor remoting a DataSet performs.