WCF extensions without including the assembly version

Question

As discussed here, I\'m trying to add a WCF endpoint-extension; I\'ve got it working, but I need to include the full assembly details:

    <         


        

Answer 1

AFAIK, it's unfortunately not possible to use partial names in the behaviorExtensions section. Strangely enough it's only for the behaviorExtensions section. For example, you can do bindingElementExtensions without full assembly name. Just looks like whoever wrote that configuration section implementation didn't allow for partial name loading where as the others did. I haven't checked to see if this is remedied in .NET 4 yet.

Answer 2

Just to reiterate what @wojo noted. If you have come here looking for the answer to

"cannot be added to this element.  Verify that the extension is registered in the extension collection at system.serviceModel/extensions/behaviorExtensions."

and you are now running .Net 4 then REMOVE the assembly Version,Culture,PublicKeyToken from the behaviorExtensions add tag. all that is needed (worked for me) was the full namespace/class followed by the assembly.

Answer 3

Have you thought about using the WCF facility for Windsor? It automagically wires extensions to service implementations when they're both registered with the container. Of course, Windsor doesn't require full assembly names. If you're not using Windsor, I'm sure you could fairly easily build an equivalent framework for other IoC containers.