4 ms·

I might be the only person who liked WCF.

• algorithmsRcool 7y ago
  I liked kinda liked it, but trying to unify HTTP, TCP, Pipes and MSMQ into a single framework was probably overly ambitious. WCF always felt very complicated with all sorts of sharp edges to me.
  • WorldMaker 7y ago
    WCF also originally supported peer-to-peer network topologies, discovery methods like PNRP (Microsoft's competitor standard to eventual "winner" Bonjour/mDNS), various versions of the SOAP metadata formats, and WS-* standards, etc. It was definitely ambitious. When it worked it was sometimes magic, and when it didn't it was a giant mess to resolve. [ETA: In one past life I made the mistake of trying to use WCF Peer-to-Peer for a project and I still have scars from that. :O]
  • paulio 7y ago
    It has a steep learning curve, true. I personally like sharing `interface.cs` rather than what appears very similar `interface.proto` plus a bunch of tooling. Ahh well, things go in circles I guess.
• flukus 7y ago
  I liked WCF, but .net devs insisting on using it to create pointless separate physical layers for web apps dulled my enthusiasm. Resume driven development in it's highest form.