Howard asks: has anyone managed to programmatically connect to the #npu on their Surface Laptop?

Note that most of the examples online of people claiming to do this in fact *fail* to connect and actually use the fallback mechanisms.

https://bsky.app/profile/hvr.endj.in/post/3lbtnbuunkc2o

Anyone in #dotnet land know how to persuade the dotnet/runtime build to emit code coverage?

Changing directory to the target test project (in this case System.Text.Json.Tests) and running

dotnet build /t:Test /p:Coverage=true /p:BuildTargetFramework=net10.0

did not seem to work; it spat out the coverage report, but there's no data (and it doesn't even include content at all for the JsonMarshal.* methods that are in the assembly, but not in the STJ namespace)

Curses. I was going to submit a session on the perf improvements we get from .NET 9 for #dotnet conf, but the CFP closed 10 hours ago!

If anyone would be interested in such a session, maybe I'll organise a short online seminar or something?

Ping me a DM or reply here, or [email protected] if you think that would be interesting.

We've just shipped Preview 10 of Corvus.JsonSchema, our low-allocation, high performance code generator and validator for #json and #jsonschema on #csharp and #dotnet.

This preview is preparing for the .NET 9.0 wave, and takes a dependency on the RC1 preview System.Text.Json libraries. Don't worry, it still supports netstandard2.0 and net8.0!

If you run on .NET 8 we get a 13% perf improvement on our "typical usage" benchmark.

.NET 9 has a whopping 32% perf uplift.

https://www.nuget.org/packages/Corvus.Json.JsonSchema.TypeGeneratorTool#versions-body-tab