No. Not for the reasons you think. Obviously, keeping with NuGet best practices (authoring, versioning, vulnerability scanning, and so on) is best for your organization. It helps set and keep …

Debugging with Visual Studio has made coding so much simpler that developing without the same level of simple integrated debugging is practically unheard of. And yet that's exactly what development …

NuGet packages need to be checked and verified before use – everyone knows that. But how can you balance security checks with your packed schedule? It's simple: create a filter …

Getting a NuGet reviewed and approved is frustrating and restricting even when the process goes smoothly. Consuming third-party packages straight from NuGet.org is bad. But how should someone request a …

If you have any experience with NuGet packages, you know that you don't need to stress about every vulnerability in every package your team is using. Even "critical" vulnerabilities are …

Microsoft's NuGet package authoring best practices is a fantastic resource for learning how to create free, open-source packages that you will publish to nuget.org. However, a lot of the advice …

CI/CD for NuGet packages isn’t just a pain – it sometimes feels downright impossible. Many teams get frustrated at CI/CD for their NuGet pipelines since it conflicts with the best …

Improperly versioning your NuGet packages can lead to lots of problems. Usually, it’s just headaches and wasted time from confusing and “broken” packages. But sometimes, this will lead to production …

Does anyone on your team treat Visual Studio like an App Store? Hastily picking out NuGet packages to use and carelessly scrolling through the terms and services just to hit …

Open-source packages on NuGet.org are a part of nearly every single modern .NET application... and most certainly, some of the ones you and your team develop. NuGet is easy to …