Chris Sainty comments

Results 185 comments of


                                            Chris Sainty

Proposal for Blazor PDF viewer

Ok no problem. I don't think this is something I can undertake at the moment either. But it's a good suggestion and I'll leave the issue for when time is...

Proposal: Blazored/Popover Repository

Thanks for the proposal Taylor. I want to understand exactly what we're aiming for if we went ahead with this package. Popovers as per the Bootstrap example you linked to,...

Proposal: Blazored/Popover Repository

This is exactly the sort of thing I was thinking as well. I agree with the approach you mention, passing ChildContent would give the maximum flexibility. Do you have an...

Blazor navigation and saving of object

Hey, sorry I've only just seen this. So as far as I'm aware, right now there is nothing in the framework that is going to help you deal with this....

Migrating ASP.NET webforms (and jquery) to Blazor

Thanks for the mention @rockfordlhotka! If you have any question about Blazored @Chicagoan2016 please let me know. 🙂

Migrating ASP.NET webforms (and jquery) to Blazor

Thank you @Chicagoan2016 😁

I can't debug, it seems like it's in Release mode

I'm not sure what the issue is. I don't use Visual Studio, I use Rider so I'm not familiar with its current qwerks. I'd suggest raising something on the ASP.NET...

Consistent issues with Getting or Setting items due to unmanaged SignalR exceptions. Re-opening issue #47 as it is the cause and was never fixed.

@Bond-Addict During your testing, did you look at the message size produced from your payload, or have you just focused on the payload size?

Consistent issues with Getting or Setting items due to unmanaged SignalR exceptions. Re-opening issue #47 as it is the cause and was never fixed.

The reason I ask about message size vs payload is that there is an overhead to encoding a payload for sending over SignalR. So even though the payload is below...

Consistent issues with Getting or Setting items due to unmanaged SignalR exceptions. Re-opening issue #47 as it is the cause and was never fixed.

> Based on my research it sounds like its possibly due to the SignalR connection not being closed and then a follow up call being made to that connection. The...