Why don't we use WCSF?

The Model-View-Presenter adoption is back to discussion on my company. And it couldn't happen on better time, as Web Client Software Factory Hands On Labs was just released.

When reading it, it was clear why WCSF adoption is so weak: usage is too complex compared with the simpler event driven model. Too many steps and too many code doesn't seem to compensate the isolation, testing and reusability advantages. Programmers have to be educated, and changes propagated to more files . But probably the bigger adoption obstacle, as I've mentioned earlier, is lack of out-of-the-box support in Visual Studio. When this happens we will have productive factoring and refactoring tools, and above all, programmers will be educated on this paradigm.

No wonder so many choose to implement the MVP pattern on their own...