Thinking of scrapping WCF technology - Please advice
Posted on 2011-10-14
I have no doubt that WCF is a great piece of technology but it has caused nothing but headaches. I work as the sole developer for a non-profit. We outsourced a company to build a large asp.net application that required a team of developers nearly a year to code. I am constantly running into WCF configuration issues. It seems as if there are all kinds of limitations on how much data you can pass through the WCF. Usually the problems can be resolved by adjusting certain settings to their maximum value. But what happens if you set everything to its maximum and it still doesn't work. I feel like I may be trying to fix something that can't be fixed because it's trying to do something that may not be possible.
So now I'm thinking that anytime I have an issue related to WCF, I'm just going to re-write the page where the error occur to not to use WCF. I could do this much quicker than debugging WCF issues. In a perfect world we would have half dozen developers. The reality is that we have one developer (me), this particular WCF issue I'm working on now has already set me back a week. That means all development within our non-profit has come to a halt and all of my development projects are now a week behind.
Has anybody experienced similar headaches with WCF, and if so how did you solve them?