Should we use WCF for this distributed application?

Question

0.00/5 (No votes)

See more:

Hi All,

I'd like to ask the advantages and disadvantages of using WCF for an upcoming project.

The project is a distributed application can be accessed via a PDA (Windows Mobile) and on the Web. We've already decided to use .NET - C# and ASP.NET. The application is also communicating with an external system (SAP).

With this in mind, we are looking into different implementations to use. One of these is using WCF to implement SOA. Since the application is being accessed through 2 different means (PDA and web), we're thinking its better to use WCF since we can create one service for both ends.

Since this is the first time we will be using WCF, I'd like to ask the opinions of those developers who had experience with this.

What are the advantages we can gain by utilizing WCF, in terms of say development, maintenance, extensions?

What could be the possible pitfalls and limitations ? We already suspect we'll encounter some problems with the PDA component.

Any advice or sharing of knowledge/experience would be welcome. Thank you!

Posted 21-Jan-12 3:43am

01xedoc

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)

jschell · Answer 1 · 2012-01-28T05:50:00

If it matters at all it probably depends on the scope.

I suspect you can use WCF at both ends. However you can also use it only at the server end. Then code the PDA app to access it as a regular web app.

One advantage to that is that it proves the interface for remote devices so you have the option of using a different remote device that doesn't support .Net.

Other than that I haven't found any significant problems with WCF as long at one doesn't expect too much from it. The exotic protocols are basically hacks and error reporting is simplistic.

Normally if one was doing a large base rollout (if that is your case) then jumping on a new technology is not advisable but if one is careful with WCF (actually the documentation for the configuration options and base it on the enterprise) then it can be pretty usable even for significant traffic.

If it is a small rollout then it would seem like a good place to at least try out WCF. On a small rollout it would be pretty hard to mess it up (with the normal protocols.)

NandaKumer · Answer 2 · 2012-01-28T09:14:00

Solution 2

check this blog
http://forums.asp.net/t/1480028.aspx/1[^]
--NDK

Posted 28-Jan-12 9:14am

NandaKumer