Sponsored By Aspose - File Format APIs for .NET

Aspose are the market leader of .NET APIs for file business formats – natively work with DOCX, XLSX, PPT, PDF, MSG, MPP, images formats and many more!

Are you using WCF within your organization?

Do you use WCF within your organization either for internal apis for exposing services and functionality to 3rd parties? We’re looking to connect with customers using our stuff in the real world so we can understand your use cases, the things you’ve liked about WCF and where you’d like to see us improve / go further. If interested, please contact me.

We look forward to hearing from you.

This entry was posted in WCF. Bookmark the permalink. Follow any comments here with the RSS feed for this post.
  • Chinedu Okoli

    Contact link does not work

  • George

    I’ve been successfully using it since 2007. I agree when it first came out that it was a bear to configure and get working but I believe that with the current version and VS 2010 it has taken a big step in making it easier. I really doubt I will ever go back to just creating web service.

  • Daniel Griffin

    I guess my experience is much different than most so far here. I’ve been using WCF for years with great success. We’ve used it for interaction with other stacks internally and externally (java, Oracle/Bea service bus eg) We’ve used basic authentication, Windows authentication, as well as Indentity framework for security. I don’t get the comments so far. Yeah it can be much more complicated, but therein lies the power. Maybe certain young jedis don’t understand the power of trhe force yet?

  • John Simons

    Currently migrating from WCF to NSB.
    WCF is just not reliable enough.

    I would like to see a better implementation of async calls.
    And yes please, remove the complexity of configuring it!

  • http://nikosbaxevanis.com Nikos Baxevanis

    In the beginning we used plain WCF. That means, messing with the element, exposing endpoints, all the ABC stuff in general. We then moved to the open-source “Agatha-rrsl” project (which uses WCF underneath). It abstracts the ABCs and you can go using a single endpoint. We stick with that, so yes, we use WCF with great success (just it’s too complicated but thanks to Agatha, this is not an issue any more).

  • Steve

    So…is moderated comments turned on, or does Code Better have a really poorly written cache?

    Its practically impossible to get any real discussion going on this site since it takes hours for a comment to show up.

  • Steve

    I’ve used it in the past with decent success, and am currently mandated with using it in the near future at my current employer.

    Let me just say that anything outside of using Windows Authentication for security is way to much work.

    I’ll send you an email through contact link you provided, because I don’t want this to turn into a complete bitch session. But using WCF is bar none the worst part of my job, and by a large order of magnitude. From config hell, to the fact that the In Code hierarchy of WCF calls doesn’t even remotely match the XML, to the fact that there are literally no good Username Authentication examples to be found anywhere.

    If I had it my way, I’d just build some RESTful Services in Sinatra and move onto something else, but being a Microsoft Shop, we need to use WCF and since SOAP offers extra goodies, I have to use wsHttpBinding.

    I guess that did turn into a bit of a bitch session after all. :)

  • http://callicode.com/ Javier Callico

    I’ve been working with WCF for a while mostly to implement Enterprise SOAP services. One of the main problems I’ve found is the DataContractSerializer shortcomings when compared to the XMLSerializer.

  • http://www.relayhealth.com PBernhardt

    We’ve been using WCF successfully for over 4 years now, both for our internal APIs and for exposing service interfaces to our partners (using java, php and .NET clients).

    Right now we are particularly interested in exposing REST-based interfaces for third-party developers. Our primary concern is 1. Security and 2. A painless developer experience, in that order.

    Right now I’m studying OAuth 2.0 and HATEOAS. Where is WCF with respect to this …. ?

  • tcmaster

    Sadly my team is forced to head to wcf by some stupid-never-code-architect…

  • Brett

    I use WCF, but agree its too much work for simple stuff. WCF is *incredibly* powerful and complex, but its too COMPLICATED. The configuration info is immense (not to mention a PITA if you want to hide away your web service client code in libraries). It seems that *MOST* people want to make http/https services, but WCF makes that extra difficult. WCF4 supposedly makes this better, but I’ve dug into it yet. I’d like to see some focus/descriptions/articles dealing with making WCF http(s) services for the intranet, that don’t involve TCP. WCF services for consuming and exposing Java web services in the Enterprise environment is a win, but most groups in our organization find that its rarely worth the effort to use WCF vs. old school asmx.

  • http://codeofrob.com Rob Ashton

    We’re using it for communication with the ESB, as well as for some inter process communication on one of our worker processes.

    Can’t say it’s really central to anything in the scope that you’d be talking about though :)

  • Jim Sowers

    We gave it up. I needed to interface with an IBM websphere web service speaking soap 1.1 and it was terrible trying to get it to go. The websphere server added namespaces and wcf would not handle it easily. I had a terrible time even trying to get into the call stack to catch the soap envelope and modify it so it would talk to wcf. I tried writing a custom attribute to get ahold of the message body. It was awful. After working at it for 3 days, I spent 45 minutes spinning up an asmx web service and it all worked with no fooling around . Everyone I talk to is abandoning wcf.