Here is how you can test out and configure timeouts in WCF more easily. The timeouts are configured in the client project.
First off, Image proof or it did not happen. Here you see that I get a timeout after already 15 seconds so how did I do that ?
[![Quick timeout for WCF client][1]][1]
[1]: https://i.stack.imgur.com/JIHHk.png
Note, I use the following Nuget packages for the client, which is a .NET 6 console application:
<ItemGroup> <PackageReference Include="System.ServiceModel.Duplex" Version="4.10.*" /> <PackageReference Include="System.ServiceModel.Federation" Version="4.10.*" /> <PackageReference Include="System.ServiceModel.Http" Version="4.10.*" /> <PackageReference Include="System.ServiceModel.NetTcp" Version="4.10.*" /> <PackageReference Include="System.ServiceModel.Security" Version="4.10.*" /> </ItemGroup>
The server project uses these Nuget packages, I have made client and service WCF from the CoreWCF templates :
<ItemGroup> <PackageReference Include="CoreWCF.Primitives" Version="1.*" /> <PackageReference Include="CoreWCF.Http" Version="1.*" /> </ItemGroup>
Inside Reference.cs, the auto-generated file on the client we got this method:
[System.Diagnostics.DebuggerStepThroughAttribute()] [System.CodeDom.Compiler.GeneratedCodeAttribute("Microsoft.Tools.ServiceModel.Svcutil", "2.1.0")] public partial class ServiceClient : System.ServiceModel.ClientBase<MyService.IService>, MyService.IService { /// <summary> /// Implement this partial method to configure the service endpoint. /// </summary> /// <param name="serviceEndpoint">The endpoint to configure</param> /// <param name="clientCredentials">The client credentials</param> static partial void ConfigureEndpoint(System.ServiceModel.Description.ServiceEndpoint serviceEndpoint, System.ServiceModel.Description.ClientCredentials clientCredentials);
//more code
We make note of the namespace of the client and add the following partial class with a configured set of timeouts. Adjust as desired these timeouts. I add a file called ServiceClient here, the class name matches the ServiceClient class name in the Reference.cs also.
namespace MyService { public partial class ServiceClient { /// <summary> /// Implement this partial method to configure the service endpoint. /// </summary> /// <param name="serviceEndpoint">The endpoint to configure</param> /// <param name="clientCredentials">The client credentials</param> static partial void ConfigureEndpoint(System.ServiceModel.Description.ServiceEndpoint serviceEndpoint, System.ServiceModel.Description.ClientCredentials clientCredentials) { serviceEndpoint.Binding.OpenTimeout = serviceEndpoint.Binding.CloseTimeout = serviceEndpoint.Binding.ReceiveTimeout = serviceEndpoint.Binding.SendTimeout = TimeSpan.FromSeconds(15); } } }
Timeouts set here is set to 15 seconds. Obviously, you would like to have these timeouts perhaps a bit longer, I only entered a small value to quickly test it. Default values are usually either 30 or 60 seconds, in production you might consider many minutes in case your servicemethods should perform long running jobs - or consider a framework for this such as Hangfire instead.
The benefit of this approach is that if you update Reference.cs (which is still a bit cumbersome in VS 2022, not as easy as in ye ole days with WCF in .NET Frmaework), your configured settings are still kept. By setting the endpoint binding you can do a lot of other configuration too.

As of now, more and more WCF users are moving into ASP.Net Core , so I added also a guide here how to increase timeouts using CoreWCF, although the approach should also work with WCF.
Here is how you can test out and configure timeouts in WCF more easily. The timeouts are configured in the client project.
First off, Image proof or it did not happen. Here you see that I get a timeout after already 15 seconds so how did I do that ?
[![Quick timeout for WCF client][1]][1]
[1]: https://i.stack.imgur.com/JIHHk.png
Note, I use the following Nuget packages for the client, which is a .NET 6 console application:
<ItemGroup> <PackageReference Include="System.ServiceModel.Duplex" Version="4.10.*" /> <PackageReference Include="System.ServiceModel.Federation" Version="4.10.*" /> <PackageReference Include="System.ServiceModel.Http" Version="4.10.*" /> <PackageReference Include="System.ServiceModel.NetTcp" Version="4.10.*" /> <PackageReference Include="System.ServiceModel.Security" Version="4.10.*" /> </ItemGroup>
The server project uses these Nuget packages, I have made client and service WCF from the CoreWCF templates :
<ItemGroup> <PackageReference Include="CoreWCF.Primitives" Version="1.*" /> <PackageReference Include="CoreWCF.Http" Version="1.*" /> </ItemGroup>
Inside Reference.cs, the auto-generated file on the client we got this method:
[System.Diagnostics.DebuggerStepThroughAttribute()] [System.CodeDom.Compiler.GeneratedCodeAttribute("Microsoft.Tools.ServiceModel.Svcutil", "2.1.0")] public partial class ServiceClient : System.ServiceModel.ClientBase<MyService.IService>, MyService.IService { /// <summary> /// Implement this partial method to configure the service endpoint. /// </summary> /// <param name="serviceEndpoint">The endpoint to configure</param> /// <param name="clientCredentials">The client credentials</param> static partial void ConfigureEndpoint(System.ServiceModel.Description.ServiceEndpoint serviceEndpoint, System.ServiceModel.Description.ClientCredentials clientCredentials);
//more code
We make note of the namespace of the client and add the following partial class with a configured set of timeouts. Adjust as desired these timeouts. I add a file called ServiceClient here, the class name matches the ServiceClient class name in the Reference.cs also.
namespace MyService { public partial class ServiceClient { /// <summary> /// Implement this partial method to configure the service endpoint. /// </summary> /// <param name="serviceEndpoint">The endpoint to configure</param> /// <param name="clientCredentials">The client credentials</param> static partial void ConfigureEndpoint(System.ServiceModel.Description.ServiceEndpoint serviceEndpoint, System.ServiceModel.Description.ClientCredentials clientCredentials) { serviceEndpoint.Binding.OpenTimeout = serviceEndpoint.Binding.CloseTimeout = serviceEndpoint.Binding.ReceiveTimeout = serviceEndpoint.Binding.SendTimeout = TimeSpan.FromSeconds(15); } } }
Timeouts set here is set to 15 seconds. Obviously, you would like to have these timeouts perhaps a bit longer, I only entered a small value to quickly test it. Default values are usually either 30 or 60 seconds, in production you might consider many minutes in case your servicemethods should perform long running jobs - or consider a framework for this such as Hangfire instead.
The benefit of this approach is that if you update Reference.cs (which is still a bit cumbersome in VS 2022, not as easy as in ye ole days with WCF in .NET Frmaework), your configured settings are still kept. By setting the endpoint binding you can do a lot of other configuration too.