I have two WinForm apps foo and bar that run on the same machine.
foo opens bar (via System.Diagnostics.Process.Start("bar.exe"))
foo needs to pass an object (of type System.Data.DataTable) to bar.
Is it best to open a remoting channel between foo and bar (with bar acting

Is .NET remoting inherently multi-threaded or do we need to implement
multi-threading in the remote object?
I need to create a dynamic number of Singleton SAOs based on an id passed
from a client. Each remote server object will maintain a different list but

The following code causes "Specified cast is not valid" exception when line
3
executes inside an ASP.NET application. I have tried this with several
components. Exactly the same code works if

I built a small app in C#. I'd like to start distributing it just for fun. I
would also like to control its distribution and be able to update some of
its dll's. Thus, I'd like to have some of the dll's be downloaded each time
the app is run; i.e., I don't want these dll's to ever ...

I have a 3rd Party COM object that requires it be run remotely on Server
"A").  I have a web application that will be running on Server "B" that will
need to create an instance of the COM object on Server "A" and execute
methods of that object etc...

I am trying to get several client apps to upload files to my server
app.  I am using Networkstreams and Remoting.  The Remoting part is
working great.  I am using Network streams for large binary file
transfers. (Let me know if there is an easier way to transfer files in

I'm using a sort of MBR method to MBV a [Serializable] object back to the
client:
ProductSupport.WorkOrder pswo = ps.CreateWorkOrderObject();
The creation of the object on the server is happening no problems. I can see