#WCF

#WCF is like Charlie Brown and Lucy with the football. You keep thinking it's going to get better.

The #WCF loves config in a pathological sort of stalker way, but never discovered the configSource attribute. WTF?

#WCF automatically adds an endpoint with the *wrong* binding for you if you screw up the config. Instead of throwing an error. Gee Thanks.

#WCF config. How do you know it's wrong? You've seen the config broken so many ways, you just feel that it's wrong.

The #WCF library has TDD beat-it throws exceptions before any tests & before you write code. Going from red to red has never been easier

#WCF routing is a wrapper around the EndpointNotFoundException.

The user time saved by higher performance of the netTcpBinding may never outpace the man years lost to #WCF config tweaking.

In #WCF 5.0 you will be able to write an app in config. In a simple 2 million line .config file you can create an entire payroll application

In the future, world-wide, all work and leisure will be replaced with time spent configuring #WCF

JSON over #WCF. Seems like a good reason to use WCF intra-application (i.e. not across organizational boundaries)