Chet Husk
banner
chethusk.bsky.social
Chet Husk
@chethusk.bsky.social
Functional Programmer. .NET SDK/MSBuild/Templating PM @microsoft. @IonideProject contributor. :heart: F# and Linux. he/him.
I've seen it on Windows and macOS, but not frequently enough to have any sense of root cause. It's incredibly annoying when it does happen though :-/
November 25, 2025 at 8:29 PM
Exposing commands that return JSON, and shipping a JSON description file with the CLI that tells DSC how to fit the various dotnet CLI commands for managing tools into its model. I pointed the folks at OpenCLI because there's a lot of shared ground too.

Still a lot of specifics to untangle though
November 19, 2025 at 12:01 AM
I was just talking to some folks today about dotnet SDK Tools being DSC3-compatible....
November 18, 2025 at 10:02 PM
uh that's weird.

--interactive should be the default in .NET 10, and it should just be flowing to the --property:NuGetInteractive=true that's passed to the Restore Task that NuGet consumes....

got a binlog?
November 18, 2025 at 5:49 PM
Gotcha - I like the rid partitioning for that too. In previous releases we'd have folks like the ONNX trying to bundle platform specific models into one package and blowing their size limits. That's sorta solved now!
November 12, 2025 at 5:44 AM
Say more @vcsjones.dev!
November 12, 2025 at 3:04 AM
Could we use something like github.com/baronfel/msb... to prototype/explore? One thing I found with this exporter is that there's SO MUCH data that you drown pretty quickly. Having a better idea of what's actually relevant for specific scenarios would help me a lot.
GitHub - baronfel/msbuild-otel-exporter: A CLI exporter for emitting MSBuild structured logs as OpenTelemetry spans
A CLI exporter for emitting MSBuild structured logs as OpenTelemetry spans - baronfel/msbuild-otel-exporter
github.com
November 8, 2025 at 10:38 PM
Woah woah woah let's not get crazy now. We don't have Activity reporting of any kind yet in MSBuild so that's a bigger lift.

What would you want to use that data for? I've had this on my personal backlog for a long time but haven't found a good motivating end to end use case.
November 8, 2025 at 9:54 PM
In a structured way that we can grab. Imagining something like a `--logger:@nuget:MyLogger` kind of experience, where something about the _identifier_ tells tooling how to locate/acquire it. Of course there are other pathways too.
November 8, 2025 at 9:09 PM
I was chatting a bit with @joelverhagen.com about related stuff a while back for my combo tool+library idea. There's some package validation stuff on the NuGet client (and maybe server?) that may need to be loosened, but there's a world where you can upload packages containing loggers...
November 8, 2025 at 9:09 PM
No because I have to do _real_ work during the week - weekends are for crazy hacking around!
November 8, 2025 at 7:18 PM
Oh I just found it, no worries :)
November 8, 2025 at 7:02 PM