I have a medium-large app that "manages" a commercial application we use. The
commercial app has a script facility that will be calling a COM-wrapped
assembly that I want to send messages via a remoted object to our manager app
acting as the server. The server app is a Windows form app with several
windows and a lot of functionality that needs to process the info coming from
the client. Everything is running on a single machine with just one instance
each of client app and server app.

How do I set up the remote object and the server so that the object can
interact with the server app and pass a couple of parameters to one of many
functions it needs to run, and then receive a True/False response back from
the server as the status to pass back to the client?

I need information about which project references what and how the remote
object and the server need to be structured. (Right now I have a VB.NET
solution with the server app and the COM class library, and a separate
solution with the remote object in it.) I can't figure out how the remote app
can access the host, and can't find documentation on just what sort of
context the remote obj is running in. Whose process and what other objects
are available?

Sorry to say that time is very tight on this, so I appreciate any quick
answers you can give me. I've been programming since shortly after they
invented the electorn, but am fairly new to .NET. I'm sort of on my own in my
department, and not actually part of I.T. in the larger organization, so I
don't have many resources close at hand.

Thanks
--
John Beaver
"It all started with a mouse."