We still have a lot of WCF services running in our backend. When we first built them, there was no ASP.NET Web API. The WCF doesn't really do anything special for us, though. We are pretty much just using HTTP transport with no special settings. We're going to migrate all the WCF endpoints to REST, but it is annoying because they work fine as they are. It's just a chore to change them all just to end up with it working the same as it did originally.
WCF is super-powerful (and super-complicated because of it). There are probably people out there that are using the really complicated features and for them transitioning out of WCF is probably a real issue.
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.
We still have a lot of WCF services running in our backend. When we first built them, there was no ASP.NET Web API. The WCF doesn't really do anything special for us, though. We are pretty much just using HTTP transport with no special settings. We're going to migrate all the WCF endpoints to REST, but it is annoying because they work fine as they are. It's just a chore to change them all just to end up with it working the same as it did originally.
WCF is super-powerful (and super-complicated because of it). There are probably people out there that are using the really complicated features and for them transitioning out of WCF is probably a real issue.