Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a .Net app running.
I want another .Net app to connect the the first app and call public methods on one of its objects.
I know I can do this via WCF, but my understanding is that .Net objects are all components in the COM sense, and so I assume can be marshalled across process boundaries on the same machine.
Is this possible? And if so how do I get hold of the object in the first app from the second?
Many thanks for any help.
Any object that inherits from MarshalByRefObject can be accessed across process boundaries (this is different from being COM visible though). This is what wcf will use under the bonnet.
However, if you use wcf instead of (lower-level) Remoting then you allow the long-term option of crossing machine boundaries (remoting does allow you to do this too, but it’s even more convoluted than wcf… edit – and less secure too, as noted in the link provided by daniel in the comments below).
In short, I agree with Daniel – you’re better off sticking with WCF – for future options and ease of use.