Loving Rx.​NET interoperability with Tasks.

Below, I could turn each event subject into a Task and use Task.WhenAny instead of Merge (I still prefer the latter).

In other cases I do filtering, throttling, debouncing on a merged stream of events.

#rxnet #dotnet #reactivex

#TIL #dotnet, using `dotnet tool install --local` for predictable Azure DevOps and local builds.

It could have been a blog post, but I don't have time right now, so just updating an old GH comment of mine:

https://github.com/dotnet/sdk/issues/8999#issuecomment-1212623125:~:text=Updated%20for%20those%20who%20may%20end%20up%20here

#TIL, Intel Driver & Support Assistant sits in the system tray and outsources all the UI to the default browser.

Apparently, they just did not want to deal with any native Desktop UI at all. So the workflow is this:

Headless .NET desktop agent app ⇔ backend ⇔ desktop browser for UI.

#Windows #Desktop

I was just asked to "deprecate" a little side project of mine, because #PowerToys has now implemented a similar feature 🥲

https://github.com/postprintum/devcomrade/issues/42

Every time I deal with this bug feels like the first time. Just wasted more than an hour debugging it.

And I know I'll be stepping on this same rake again and again. #dotnet #csharp

I'm working on a MSI installer builder app for for a self-contained .NET 7 WinForms app (`dotnet publish -r win10-x64 -c Release --self-contained true`)

It's packaging all the published assemblies.

Now I'm about to sign it and I wonder if I should only sign the produced MSI file and the main EXE file inside it, or all the Microsoft and 3rd party binaries?

#dotnet #msi #wix #winforms

I don't think I need T4 anymore. Multi-line string literal in C# 11 will probably cover all my use cases.

On a side note, many thanks Rob Mensching and the team for all their tireless work on WiX v4: https://github.com/wixtoolset/wix4

#dotnet #csharp

(RT: https://twitter.com/noseratio/status/1596060829572812800?s=20&t=T-8K8C7bvU5HEK-hxf2Jxw)