NuGet Supply Chain Attacks: How Malicious Packages Compromise Your .NET Build Pipeline (and How to Reduce the Risk)
Code Every claim below is backed by a test, not a blog-post assumption — the build-time...
Tag archive
Code Every claim below is backed by a test, not a blog-post assumption — the build-time...
The Version Alignment Dilemma When a team faces an internal platform migration from .NET 8...
The SemVer Specification Reality: What the Rules Actually Allow If you trace the literal...

When you work simultaneously with APIs, databases, and frontend applications, it’s almost inevitable...
Last month I shipped Nugetz.dev. It’s a modern interface for searching the NuGet registry. This...

Pennyforge studio — zero-cost audit, all sources fetched 2026-10-05/06, reproduction at the...
You have v1.2.0 and v1.3.0 of a DLL and need to know exactly what changed — new APIs, a silently altered method, a fresh network call — without the source and without running either build. Here is how to diff two assembly versions in Glass.NET, the free, static-only .NET decompiler.

Bundling NuGet Package Dependencies in an SSIS Script Task If you've ever tried to...
Five write-ups, one week, and the patterns that kept showing up when the hype was stripped...

Aprenda a publicar uma biblioteca .NET no NuGet.org com SemVer, validação no ambiente de teste e feeds privados no Azure Artifacts e GitHub Packages.
A NuGet package ships compiled DLLs, not the source you read on GitHub — so the only way to audit the exact code you are about to run is to decompile it. Here is how to decompile a NuGet package back to C#, what red flags to look for, and how a free decompiler makes the review fast.
The Problem In one of our Azure DevOps pipelines, nuget restore suddenly started failing with an...