Server Message doesn't come to Client.

[burkut]

hallo,

i have following Problem. Is there anybody, who can help me or can give some suggestions?
i want to create an AddIn in EA. So i have used the Automation Interface with C# in the following linkhttp:// http://www.sparxsystems.com.au/resources/developers/autint.html.

the Background of this Programming is that i want to create a kommunication between EA and my Application. My Application is hier a lokal Server(f.e. Windows service). For that Automation Interface of EA shloud be a Client of my Server. So i have written in C# a Client Connector class so that it uses .Net Remoting and creates a connection to the Server. The connection can be created und i can send Msg to the Server, the Server can process it so it was intended to. All these are ok. The Problem is here:

the Server can send the processed Msg to the Client (also to Automation Interface ) but my Client can't receive the Msgs anyway. there are noch Bugs too. It disappears without any Bugs or something like warnings... (I am using for the Return Channel the Callback Mechanism.), the Strange thing is hier, i can receive the Message, if start my Client without Automation Interface, also as independent(Windows or Console) Application. So it works fine. No other Problems.

it is so mysterious, so that i can't find out the reasons. I am very gratefull, if anybody helps me on this problem.

Thank you for time.

Burkut

PS:
1.I am using VS 2008.
2. Settings for A utomation Interface with C# are same in the README in the Zip file.

[g.makulik]

Hi burkut,

My knowledge about that (.NET Remoting) stuff starts to get rusty already, just some ideas:

• How's your .NET remoting configuration for your other client samples done? Manually or using a configuration file? If the latter, can it be accessed from the EA addin client?
• May be it's some .NET security issue

What exactly do you mean with 'it disappears'? That your client using the EA automation interface crashes, after the service sent the processed msg back? And it does so without any exception thrown?
Could you debug to the point where the client is waiting for the server response (the callback)? Did you enclose this in a try/catch block to inspect exceptions that may occur there?
It's also can be a pretty different thing to have a standalone application (e.g. like a console app) and a .dll thats runnung in another applications (EA in your case) context.
It's hard to say, but I don't really think, running your app as EA AddIn makes up the primary problem.

HTH
Günther

[burkut]

Hi Günther,

My .NET remoting configuration for my all client samples done by Manually. unfortunately i can't get any Message such Security isues, bugs, warnings .... etc. nothing i can get, so i can't say the problem is there or here.
I mean with "Disappearing Message" that i can't get any trace(bugs, warning or something like that hints to me know what was happened after i send the message) of it.
you are right there is no exception too. i can debug to the point, where ther server send the message and i know that the Callbackobject of Client is still alive, und next debuggingstep no reaction on both sides. the break point on the client has no effect, i mean the Sever message does not come to there.

you have said, you have seen some examples like that for MS Word something, can you please give the links for the examples if you find please?

cheers

Burkut

[Makulik]

Hi,

you have said, you have seen some examples like that for MS Word something, can you please give the links for the examples if you find please?

I've just seen such stuff being mentioned in forum threads, e.g. that one for the 'Spearfish Plugin' that uses a M$ Word backend for maintaining Use Case descriptions AFAIK. I think there's even a sample for such thing available on the Sparx resources page. I didn't delve into these deeper.
But anyway,  just using another automated app is pretty different from communicating with a windows service process. And all that .NET remoting stuff can be tricky and can produce hard to track and subtle issues as far I remember.
Sorry, that I can't be more helpful for you here.

WBR
Günther