NuGet
NuGet NuSpec Fields Explained: Dos and Don’ts
Posted on March 12th, 2026.There are many metadata fields in a NuGet Package. For first-party packages, you can avoid 8 and not have any problems in your development.
There are many metadata fields in a NuGet Package. For first-party packages, you can avoid 8 and not have any problems in your development.
Back in 2012, a feature flag at Knight Capital accidentally turned on dormant code, triggering uncontrollable trades and a $440 million loss. This kind of failure shows how risky feature flags can be when they’re misused. If teams rely on them to feel safe instead of really understanding the change, even routine deployments can go badly...
Last year, we sent out the Inedo Snack Box to our members, and we’ll be doing the same again in 2026! Whether you run ProGet, BuildMaster, or Otter, are exploring our products for the first time, or provided feedback during evaluation, your input has helped shape what we build. At Inedo, we describe ourselves as a user-driven company....
There are three ways to express a license in a NuGet package: expressions, url, and file. This article is a quick explainer on what NuGet license types are.
Over the past year or so, the number of malicious packages has grown beyond anyone’s wildest expectations. The rapid, 10,000%+ increase has caused scaling challenges in systems like ProGet, which are designed to detect and block these harmful packages. For ProGet, this translated to timeouts and slowness when processing data...
Have you ever noticed how small, everyday issues start piling up while your team is focused on delivering those “big” or “transformative” changes? Hidden dependencies, and operational pressure build into bigger problems: backlogs that never shrink, urgent requests slipping through, and teams constantly putting out fires. What begins as...
If you work with CI/CD pipelines, artifact repositories, or DevOps workflows, you’ll be familiar with Amazon S3. It’s flexible and widely used, but as your repository grows, costs can add up fast. Storage is just one piece of it; request charges and egress fees can catch teams off guard, especially when traffic spikes. As you...
If you’re managing projects that rely on multiple teams delivering consistent components, you’ve probably noticed the chaos that comes from storing build artifacts and libraries in shared folders. Each team has its own way of organizing files, versions get mixed up, and no one really knows which asset the project should be using....
You’re likely pulling OSS packages straight from NuGet.org, npmjs.com, or PyPI.org, via the CLI. It’s the path of least resistance and the fastest way to get what your teams need. But without something sitting in the middle, it’s hard to know exactly what’s being pulled in or whether it meets your org’s requirements. When you pull OSS...
Internal registries are a smart way to manage OSS packages. They let you curate reusable code for your apps and cut down on risky repeat pulls from the wild. But when every team spins up its own siloed registry and tooling sprawls across the org, you end up with duplicate work, outdated packages, and security headaches that didn’t need...