.Net Remoting without using .Net remoting?

Question

I most recommend.

I have the following example:

Appication1.exe - has a MyList object

Application2.exe - You need to access MyList and interact with the object as if it were created from Application2.

Should I use .NET Remoting (i.e. 2.0) or WCF or another technology stack? What framework is available to support this? What are the advantages / disadvantages for each?

I should note that this is more of an assistant application and will not be used by anyone outside the development team.

Answer 1

, , WCF . WCF . API -, , , . Microsoft , WCF , , , , , WCF , .

, . . ? , , , , App 1 , 2 , ..

Answer 2

, 1 , 2 - . , , 1, 2. WCF, , . Remoting .

- , XML ?

, . 1 2? ? , ? ?

Answer 3

. WCF - , , . , App1 ( push pull) App2. , esp. App1 . App2, . , . App2. ( , , dev - ).

Remoting - , . WCF . , , WCF .

Answer 4

, .NET. - Application1 Application2, . , "MyList" MarshalByRefObject. MSDN , Remoting legecy stuff (.NET 3.0) WCF. , , Remoting - .