[Solved] Debug with a breakpoint in the OnUpdate handler leaves the grid unresponsive after a continue...

[Rob]

If I place a breakpoint in the OnUpdate handler (async) in a grid, spend about 20 seconds inspecting values (no code changes, just looking at values) and then "continue" I get the following:

The grid is now completely unresponsive ... it doesn't continue execution and I have to basically stop execution from VS 2026.  Having to return a test session every time I debug is INCREDIBLY time consuming ... there must be a better way to debug?

 

[Dimo]

Hello Rob,

You can increase the Blazor SignalR timeout period or just refresh the web page in the browser. In ether case, there is no need to restart the whole app.

Regards,
Dimo
Progress Telerik

[Rob]

Hi Dimo,

var builder = WebApplication.CreateBuilder(args);

builder.Services.AddSignalR(options => { options.ClientTimeoutInterval = TimeSpan.FromSeconds(60 * 60); }); // 60 minutes });
builder.Services.AddServerSideBlazor().AddHubOptions(options =>
{
    options.ClientTimeoutInterval = TimeSpan.FromSeconds(60 * 60);
    options.HandshakeTimeout = TimeSpan.FromSeconds(60 * 30);
});

I must be missing something because I already have this in my program.cs:

This is a Blazor-Server app.

Tried different values and it makes no difference at all.  Thoughts?

Rob

[Dimo]

Hi Rob,

Not my area of expertize, but I am not sure our configurations are equivalent. Notice the withServerTimeout setting, which I used. I don't see a counter-part in the available middleware API.