out-of-proc COM Server

David,

Yes!, It is on same machine and it is safe to assume that it will always run on the same machine. I did take a look at the URL you gave. it does not have "SystemHandleInformation" but it does have SystemProcessInformation which returns array containing Process information. Following is the code snippet that works correctly as long as only one instance is running.

private Object AccessCOMServer(String nameOfExecutable, String COMProgID)
{
Process[] proc = Process.GetProcessesByName(nameOfExecutable);
if (proc.Length == 1)
{
Type dataAppProgID = Type.GetTypeFromProgID(COMProgID);
_dataApp = Activator.CreateInstance(dataAppProgID);
String currentPath = _dataApp.GetType().InvokeMember("DatabasePath", BindingFlags.GetProperty, null, _dataApp, null).ToString();
}
}

Debugger shows

proc[0] is shown in debugger as instance of System.Diagnostics.Process with all information including process id, name of executable, path of executable and even command line arguments that were used to invoke it.

dataAppProgID is shown as instance of System.RuntimeType with many properties and assembly that originates from is shown as mscorlib
_dataApp as System.__ComObject with only visible properties Identity and m_ObjectToDataMap (Hashtable) as null
but all invoke

Even I use the second suggestion of using CreateProcess, it will execute the new instance all right and connected to correct database but how do I get the COM server to bind to correct running process.

Entire problem revolves around my limited understanding of Activator.CreateInstance which as 13 overloads and some of them do accept things like assembly domain, but Process object does not expose assembly's appdomain.