Here 
– I can certainly understand his points.  For me it comes down to two things:

1) The design of ServiceHostBase isn’t as clean as I think it should given its intended
purpose (to allow WCF Services to be exposed w/o a .NET Type associated with it).

2) The exception.  I wouldn’t hate the design as much if a) the exception wasn’t
a blatant lie, and b) they actually documented that you need to call InitializeDescription
from your constructor.



Check out my BizTalk
R2 Training.