Where to start to do a Remoting application in C#.net

Question

1.00/5 (1 vote)

See more:

Hi,

I am new to C#.net.I am looking forward to build a remoting application.I am very new to the remoting Concepts.Please help me where to start .

regards
Chaithu

Posted 1-Jun-11 20:07pm

M.CHAITHANYA

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Abhinav S · Answer 1 · 2011-06-01T20:11:00

Solution 1

If you are using .Net 4.0, you should look at using WCF instead of remoting.
Read more about WCF on the msdn website.

Posted 1-Jun-11 20:11pm

Abhinav S

v2

Comments

Sergey Alexandrovich Kryukov 2-Jun-11 2:23am

I just pointed out the same thing. (My 5.) There are advanced cases when classic remoting beats WCF, but they are not typical. Also, WCF is more suitable for starters.

Please see my links.
--SA

Abhinav S 2-Jun-11 2:24am

Can we actually implement remoting in .Net 4?

Sergey Alexandrovich Kryukov 2-Jun-11 2:35am

You mean use it, classical remoting? Or yes, sure.
--SA

Abhinav S 2-Jun-11 2:44am

But it needs to be implemented using the ABCs of WCF. Earlier Remoting had separate contructs of its own.

Sergey Alexandrovich Kryukov 2-Jun-11 2:54am

Yes of course. This is like a parallel system. Earlier Remoting and WPF are not related.
--SA

Abhinav S 2-Jun-11 7:01am

Yes. Thanks.

M.CHAITHANYA 2-Jun-11 2:33am

Hi,

I dont want to go to that high level ,as my intension is to just communicate with client programatically .How to do this?

Sergey Alexandrovich Kryukov 2-Jun-11 2:39am

Stop it! You don't know what is high level and what's not. Do you really want lower-level which is usually more difficult. You asked about remoting, not sockets. And you got best advice. What is your requirement, using exact technology or a functionality? Almost everything is to "communicate with client programmatically (or with server :-)). If you need this functionality, use WCF. See some articles I advised.
--SA

Sergey Alexandrovich Kryukov · Answer 2 · 2011-06-01T20:21:00

I would advice you to start not from "classical" remoting, but from simple cases of self-hosted WCF.

WCF is easier to start and put to work in most typical and simple cases. Classical remoting needs more effort, especially at first, when you sort out the problems of remote object activation.

If you're ready to start with WCF, try to follow the approach using these CodeProject articles:
A Quick and Dirty WCF Service and Client (Using WCF and Winforms)[^],
Simple WCF Hosting and Consuming[^],
Exploring Windows Communication Foundation - Part 2[^] (where is part I, will you find it?),
Exploring WCF 3.5 Tools - WcfSvcHost and WcfTestClient[^].

See also: http://msdn.microsoft.com/en-us/library/ms731082.aspx[^],
http://msdn.microsoft.com/en-us/netframework/dd939784[^].

—SA