Hi Akhil,
I think the remote RTD scenario is really hard to get right. I don’t have much experience with it myself, but my impression is that the Distributed COM protocol is hard to configure and make reliable on recent versions of Windows. I don’t have any samples or guides for getting it to work.
So I would strongly recommend you not to do this, but rather make an RTD server (based on the ExcelRtdServer base class) that runs in-process, and uses your own communication mechanism to communicate with the remote server (http / tcp / WCF / etc.)
If you do want to explore the DCOM remote server approach further, then Excel-DNA won’t interfere (or help) with this. Note that:
· You won’t be able to use the ExcelRtdServer base class from Excel-DNA – this won’t support the remoting approach.
· You won’t be able to use the late-registration approach (where you call the RTD function as XlCall.RTD(…)).
· You will have to make the RTD call directly via the Excel RTD function, as XlCall.Excel(xlfRtd, progid, server, topic1, topic2). This is equivalent to the worksheet function =RTD(…)
Once you have it working from a worksheet directly via the =RTD(…) function, and you then have any problems related to the add-in , I’m happy to help.
But I would not expect problems getting it to work with your add-in, once you have the basic remote functionality working from Excel.
Regards,
Govert
--
You received this message because you are subscribed to the Google Groups "Excel-DNA" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
exceldna+u...@googlegroups.com.
To post to this group, send email to exce...@googlegroups.com.
Visit this group at https://groups.google.com/group/exceldna.
For more options, visit https://groups.google.com/d/optout.