Question

Why serviceBehavior part is not generated on client side automatically after ServiceReference tool in Visual Studio as endpointBehavior?

Was it helpful?

Solution

Wsdl.exe or "Add Service Reference..." generate proxy classes, datacontracts & config based upon exposed metadata. Commons ways to expose metadata is by using a mex endpoint or exposing a wsdl.

Basically, Behaviors are simply not exposed. That's why you can't generate the same endpoint behaviors on client side.

What is important here, is that many behaviors are "local settings only" (for a service OR for a client ). It does not tell to clients how to call the service, but how the service should run.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top