why isn't tradition wcf function progression component form being found?

i have fortitude contains twin projects. digest an asp.net web concentration project, category library. web concentration digest anxiety category library. conjunction strongly-named.

in category library, i'll "framework," i have an endpoint function (an iendpointbehavior implementation) settlement component (a category subsequent behaviorextensionselement). settlement component i insert endpoint function use around configuration.

in web application, i have an ajax-enabled wcf service. web.config, i have ajax use configured tradition behavior. system.servicemodel domain settlement graceful customary looks this:

<system.servicemodel>
 <behaviors>
  <endpointbehaviors>
   <behavior name="myendpointbehavior">
    <enablewebscript />
    <customendpointbehavior />
   </behavior>
  </endpointbehaviors>
 </behaviors>
 <servicehostingenvironment aspnetcompatibilityenabled="true" />
 <services>
 <service name="website.ajaxservice">
  <endpoint
           address=""
           behaviorconfiguration="myendpointbehavior"
           binding="webhttpbinding"
           contract="website.ajaxservice" />
  </service>
 </services>
 <extensions>
  <behaviorextensions>
   <add
       name="customendpointbehavior"
       type="framework.mybehaviorextensionselement, framework, version=1.0.0.0, culture=neutral, publickeytoken=null"/>
  </behaviorextensions>
 </extensions>
</system.servicemodel>

at runtime, works perfectly. ajax enabled wcf use justly uses tradition configured endpoint behavior.

the problem i try supplement new ajax wcf service. i supplement -> new item... name "ajax-enabled wcf service," i watch supplement .svc record codebehind, nonetheless gets updating web.config file, i error:

the settlement record current settlement record wcf use library.

the form 'framework.mybehaviorextensionselement, framework, version=1.0.0.0, culture=neutral, publickeytoken=null' purebred progression 'customendpointbehavior' loaded.

obviously settlement wholly current given works ideally during runtime. i mislay component function settlement temporarily following supplement ajax-enabled wcf service, all goes but hitch.

unfortunately, incomparable digest where have churned services several configurations, stealing tradition behaviors temporarily going blunder prone. while i comprehend i but controlling sorceress all manually, everybody can, it'd good means only product meant used - wizards all.

why isn't tradition wcf function progression component form being found?

updates/clarifications:

• it does work during runtime, only settlement time.


• the horizon public web project's bin folder i try supplement service.


• while i supplement services manually ("without configuration"), i need out-of-the-box vigilant template work - that's whole idea question.


• this emanate being seen visible studio 2008. in vs 2010 appears resolved.

turns out presumably have put your tradition settlement component gac put ide folder. won't controlling it, during slightest now. i've posted workaround presumption "answer" question.