Daniel Cazzulino

I have renamed ndnx to ndx. .NET 10 shipped dnx (dotnet tool exec): one-shot nuget tools, npx-style.

I’ve been playing with the xAI API recently, and noticed something interesting about their pricing model.

TL;DR: Run remote scripts instantly with the ref format [host/]owner/repo[@ref][:path]. dnx runfile kzu/run:clean.cs With .NET 10, we are seeing continued improvements in how we can run C# code directly.

Almost exactly a year after my SponsorLink v2 post, and having virtually no traction whatsoever (besides a handful of sponsors, deeply appreciated!)

What a monumental release for .NET scripting is .NET 10!

I started playing with the MCP C# SDK soon after it came out, and soon realized that there was a gap in functionality: setting the log level in the MCP server-specific output pane in VSCode was not invoking my MCP server’s corresponding log-level change h…

SmallSharp 2.0: The End of ConsoleApplication128 The New Era: dotnet run app.cs With .NET 10, you can now run a single C# file directly: dotnet run app.cs No project file, no ceremony.

Grok 4 was just announced and it looks incredible.

Sometimes it’s useful to render VSIX manifest metadata in logs, or some UI in your extension.

As part of developing SponsorLink v2 I needed a mechanism to determine what packages in nuget.org were popular (in terms of daily downloads), as well as their source repositories and contributors.

TLDR: grab the source code or add it locally with dotnet file add https://github.com/devlooped/catbag/blob/main/OpenAI/Chat/ChatClientTypedExtensions.cs .

Almost exactly a year after my SponsorLink feedback post, I think I have worked out most of the issues and would like to give this another try with a completely rewritten SponsorLink v2.

Sometimes you need some API keys, connection strings and the like in order to run your tests.

When running dotnet test, there is no built-in mechanism to retry failed tests, and constructing the filter format for re-running them is non-trivial.

Running tests across multiple projects in a solution doesn’t have to look like the 90s in today’s console.

Whether you’re creating a brand-new .NET isolated function app or migrating an existing one, if you’re deploying it using the Azure Functions Core Tools, you might encounter this error: Your Azure Function App has 'FUNCTIONS_WORKER_RUNTIME' set to 'dotnet…

Every time I create a new CLI tool, I face the challenge of keeping the project and package readme (for dotnet tools like dotnet-trx) up to date with the evolving tool itself.

The GitHub GraphQL explorer is an awesome way to explore the GitHub API.

When using Blazor cascading values, especially root-level, the build-in mechanism will not notify other components of changes in the value properties.

As I mentioned in my introduction post on SponsorLink, open source sustainability is a tricky topic.