NuGet.org is the best place to get NuGet packages and jump-start your projects, but how can you quickly vet content when time is tight? Developers are always on the lookout …

Have you ever consulted the source code of an NuGet package for debugging? Checking the original source files used to build a package can help during the debugging process, especially …

For NuGet packages, a vulnerability isn’t the end of the world. Most NuGet users can agree that even a critical vulnerability is difficult to exploit. That doesn’t change the fact …

You’ve heard of Symbols and Symbol packages. They’re a great tool for debugging your NuGet packages – some of the most fiddley packages to debug. What’s the best way to …

There are over 25 metadata properties that can be filled in a NuGet .nuspec file. And those choices are permanent - once you publish a package, you can't edit or …

The case Artifex v. Hancom was a harsh lesson for the defendant. Unknowingly – or at least unintentionally – software with a GPL-3 license was distributed and profited off of, …

“It worked when I built it” or “It works on my machine”. These are typically followed by frustrated moans and an investigation to identify the source of the problem. Unfortunately, …

So, you set up a local NuGet feed on a network file share for your team small. But as you and the team add more and more packages to your feed, …

.NET 6 has released to much excitement for the DevOps community. So what does that mean for .NET Core 2.1, .NET Core 3.1, .NET Framework 4.8, .NET 5…? There’s a …

I’ll be straight to the point: poorly versioned NuGet packages will cause problems. A NuGet packages can have one of five distinct version numbers, all with their own formatting rules …