Any compelling reason to stay on WCF?

Question

I've been trying to create a stable web service application for the last 2-3 months. about 2 months ago I made the choice to move over to WCF to take advantage of the single instanced web services.

Since making that move I've had some real headaches deploying to IIS 6 scenarios. Unfortunately because most real clients still use Windows Server 2003 and IIS 6. I've been getting every WCF error you can possibly imagine.

Client patience is wearing thin and soon it will look like we are unable to deliver a reliable solution.

I am almost decided to move back to ASMX services that at least worked, and didn't suffer from stuff like :

The sequence has been terminated by the remote endpoint. The user specified maximum retry count for a particular message has been exceeded. Because of this the reliable session cannot continue. The reliable session was faulted.

The communication object, System.ServiceModel.Channels.ReplyChannel, cannot be used for communication because it has been Aborted

The list goes on... before I make the move back to ASMX, are there any compelling reasons to stick with WCF, because at this rate we could loose large clients over this technology?

Answer 1

Because, eventually, sites will move to IIS7?

Seriously, if WCF was built for IIS7 seems to work better under IIS7 and you have no problems using WCF with IIS7, then the choice sounds pretty simple. Stick with WCF only if the client has IIS7. Otherwise, use "older" technology with "older" technology.