25+ years as a Software Developer. I'm passionate about process improvement using technology. Let's all work smarter not harder and do more with less.
MY THOUGHTS ARE MY OWN
I'm happy it's going away. I stopped using it to create web services a long time ago. I even reverted back to .NET 2.0 web services so I would not have to use it. Then thankfully Web API came out. Most people created internal web services with WCF and set the transport method to http. That right there told me that even though MS had a vision, it wasn't communicated effectively to developers. WCF was dead from the start. On top of that, WCF configuration was way too complex. WCF was/is a jack of all trades and a master of none.
I totally agree. Why in 2019 you are using WCF escapes me, UNLESS you are doing some INTERNAL interoperability commmunication between systems that do not support http. It would have to be a special case for me to use WCF. The configuration of it is just too complex.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm happy it's going away. I stopped using it to create web services a long time ago. I even reverted back to .NET 2.0 web services so I would not have to use it. Then thankfully Web API came out. Most people created internal web services with WCF and set the transport method to http. That right there told me that even though MS had a vision, it wasn't communicated effectively to developers. WCF was dead from the start. On top of that, WCF configuration was way too complex. WCF was/is a jack of all trades and a master of none.
I totally agree. Why in 2019 you are using WCF escapes me, UNLESS you are doing some INTERNAL interoperability commmunication between systems that do not support http. It would have to be a special case for me to use WCF. The configuration of it is just too complex.