Hi Daniel,
keeping the 'path' issue for what it is at this moment, I think I've run into something more complex.
What I'm trying to do is incorporating some crude number crunching to a RxNet.dll, for example exporting a lot of entity information to a file.
Let's say I gave such a command [CommandMethod("DoIt")]
so after NetLoading the DLL I type DoIt at the command prompt and voila, magic happens.
Now I want to automate this as part of a larger process and use an ordinary COM link to the Application.ActiveDocument and call SendCommand("DoIt") to trigger the RxNet.dll.
Bad luck, bad luck, what I think is happening is this:
The COM SendCommand holds a reference (and locks?) the ActiveDocument.
When Rx tries to start the DoIt() it also tries to get a connection to the same ActiveDocument, but that fails since and external process is busy with it. ( That's at least how it feels)
Am I correct in my observation? And if so, how do I send a command or is there an other way to start the RxNet routine?
I was reviewing the presentation of Prodok at this years conference in Brugge, also mentioning DeadLocking COM calls.
Is that a way to go?
TIA,
Arno