Timeout

[dsoltesz]

I recently upgrade to version 5.0 and my app doesn't seem to be honoring my timeouts anymore..I'm hitting these 1 min timeout errors. I've had this code in place where on the client in the OnCreated method of my domaincontext I call this method to increase the timeout but doesn't seem to work anymore. Has anything changed to prevent this or is there a new way to change the default timeout?

` public static void ChangeTimeout(this DomainContext domainContext,
TimeSpan newTimeout)
{
// Try to get the channel factory property from the domain client
// of the domain context. In case that this property does not exist
// we throw an invalid operation exception.
var channelFactoryProperty = domainContext.DomainClient.GetType().GetProperty("ChannelFactory");
if (channelFactoryProperty == null)
{
throw new InvalidOperationException("The 'ChannelFactory' property on the DomainClient does not exist.");
}

        // Now get the channel factory from the domain client and set the
        // new timeout to the binding of the service endpoint.
        var factory = (ChannelFactory)channelFactoryProperty.GetValue(domainContext.DomainClient, null);
        if (factory.Endpoint.Binding != null) factory.Endpoint.Binding.SendTimeout = newTimeout;
    }`

[Daniel-Svensson]

The code required to change wcf related properties has changed for 5.0

Have a look at #267 for details of how to make modifications to the channelfactory or bindings

[dsoltesz]

Will check it out...thanks!!

[dsoltesz]

So you can only change values for ALL domain contexts in your project with the override of the CreateChannelFactory? We have 50 plus domain contexts in our .net 4.7 wpf app and difference contexts have different timeouts and other various settings. Now with the new approach it seems they all use the same factory and all have to have the same values, is that correct?

[Daniel-Svensson]

The CreateChannelFactory gets called "per type of DomainContext" with the generic parameter TContract (and the Uri) available to do customizations per service type.

If you need different customizations for different instances of the same type then I think the easiest approach is to create your own DomainClientFactory class, (you can have each call to it create a new WebDomainClientFactory and delegate the actual creation to that factory)