You can cut a few lines of code with LINQ and use a constant, yeah not much better I know.

var operations = _client.Endpoint.Contract.Operations;

foreach (var operation in operations)

{

operation.Behaviors.Find<DataContractSerializerOperationBehavior>().MaxItemsInObjectGraph = MAX_ITEMS_IN_OBJECT_GRAPH;

}

Welcome to my world.

Unfortunately I don't think there's any simpler way to do it OOTB

Extension methods are your friend

On a late-night call to a customer, we found it possible to override using machine.config (potentially app.exe.config as well, I do not recall, it was a "get-it-working-now" deal).

But our final solution was to do the override in code like you posted.

Found the support ticket.

Yep, machine.config, ugh. But potentially it may be possible to modify this at a less invasive level, I don't recall if this was possible in an application configuration file, and don't have a machine at hand to test it right now.

But the config-only workaround involved modifying <commonBehaviors> in <system.serviceModel> to look as follows:

<commonBehaviors>

   <endpointBehaviors>

       <dataContractSerializer maxItemsInObjectGraph="2147483647" />

   </endpointBehaviors>

   <serviceBehaviors>

       <dataContractSerializer maxItemsInObjectGraph="2147483647" />

   </serviceBehaviors>

</commonBehaviors>

You may see some lines in there about a Visual Studio ServiceModelSink, which you probably want to preserve, but they should not be present on a machine without VS installed.

HTH

I wrote some contract/operation behaviors that enabled be to control preserving of object references.  It also allows you to set MaxItemsInObjectGraph.  It can be applied to contacts/methods or added as a general behavior.  If you want it send me and emai @

cneuwirt@gmail.com

Derik,

You can also create a custom ServiceHost and have it populate the Endpoint behavior on ServiceHost.Open(). I can blog this soon if you need it.

I had a very similar issue yesterday: setting the MaxStringContentLength to a higher value to allow longer string content to be passed to our REST service. Since we've using a custom WCF REST + Castle solution, I've had to adjust this setting by overriding IEndpointBehavior.AddBindingParameters() method, like:

       public override void AddBindingParameters(

           ServiceEndpoint endpoint,

           System.ServiceModel.Channels.BindingParameterCollection bindingParameters)

       {

           base.AddBindingParameters(endpoint, bindingParameters);

           SetBindingQuotas((WebHttpBinding)endpoint.Binding);

       }

       private void SetBindingQuotas(WebHttpBinding binding)

       {

           binding.ReaderQuotas.MaxStringContentLength = maxStringContentLength;            

       }

Ugly, but it works. BTW I consider WCF to be an ugly technology in general, so I kind of get used to such tweaks.

Just the other day, Derik Whitaker ran into some issues setting up his ChannelFactory to handle large