Marcus

[Marcus @maloo321]

@davidfowl ensureExists or ensureCreated

[Marcus @maloo321]

@EisenbergEffect I use those, and VScode fast components, but I thought Teams and Office etc used the react ones. But I hope you are right and they will migrate. When you left FAST I saw it as a sign of Fast loosing to React ;)

[Marcus @maloo321]

@terrajobst especially records

[Marcus @maloo321]

@davidfowl I should say I don't have any deadline but I would still expect client to be notified if grpc is dropping messages in streaming.

[Marcus @maloo321]

@davidfowl Yes, looked over all config options in docs. This is an iot client with a local 4G router. And it seems to happen when it has a bad connection. I've used tcp keep alive before without issue. And device is RaspPi in field so hard to do wireshark debugging.

[Marcus @maloo321]

@RickStrahl why run in iss if it is a dotnet core app?

[Marcus @maloo321]

@praeclarum Rear ending will have a new type of ending ;)

[Marcus @maloo321]

@JetBrainsRider Ok, I'll see what we can find next week. But today we got it on a machine with 2023.1.1, and he says it comes and goes. Build finishes, but then a long delay before debugger starts. I also managed to get it in attach mode. I even attached twice since there was no feedback.

[Marcus @maloo321]

@JetBrainsRider I found the rollback feature in toolbox, back in 2023.2.1 now and debugger starts fast again

[Marcus @maloo321]

@JetBrainsRider We got huge (over 30sec) delays when starting the debugger in this release, is that a known issue? If so, will you have a patch soon or do you recommend reverting to 2023.2.1?

[Marcus @maloo321]

@davidfowl Rust like error handling (discriminated unions and shorthand return on error), cancelation w/o exception, span usage between awaits.
In box Blazor component/layout library, like FlientUI/MudBlazor but part of dotnet so companies can trust future support like winforms.

[Marcus @maloo321]

@captainsafia A product name

[Marcus @maloo321]

@davidfowl I know, I was just wondering if you liked the idea of no longer having to expose a prometheus scraping endpoint, or if you liked the idea of using push over scraping, or the idea of using a standard protocol over prometheus protocol...

[Marcus @maloo321]

@davidfowl Is it a custom prom scraping endpoint you don't like or is it scraping in general? I feel scraping is better than push... but standard better than app specific protocol.

[Marcus @maloo321]

@praeclarum @migueldeicaza My memory rule is that you can figure out that if you only give it one argument, it must be the existing thing, then you know the second is the optional new name

[Marcus @maloo321]

@DamianEdwards @davidfowl Seems like and IIS issue again, works on Linux App service

[Marcus @maloo321]

@DamianEdwards @davidfowl Do you know if Azure can handle Blazor Web App (streaming and enhanced navigation)? Or it is like with gRPC that IIS or YARP can't handle it at release? We tried publish an app working locally, and navigation fails in Azure App Service.

[Marcus @maloo321]

@EisenbergEffect Where will you publish? Will you cover versioning, maintenance (like npm rott), mixing framework versions, multi site pages using components, bandwidth reduction using WCs for SSR, WC in WASM, attribute vs property issues with non js frameworks...