In the .NET Framework Developer's Guide there is a page
titled Building a Host application.
Within this page there is a note:
Unlike COM, remoting does not start the host or server
application for you. This is an important difference
between .NET remoting and remote activation in COM.
I need this functionality.
I need to be able to start a seperate win32 process and
communicate with it.
The trick is that there must not be any need for
configuration files or such.
I could approach the problem one of two ways.
Either my client dll can reference the server exe (but
referencing an exe is not allowed by the IDE).
Or I can reference and execute a dll.
The reason I want to reference it is to make sure that VS
always puts a copy of it where I can find it, so I can
execute it.
Another possibility is to make the server app also a COM
server and just register it that way, but this is not
managed and VS will not register an exe this way.