Many long-lived .NET repositories did not start with semantic versioning. They grew up with major.minor.build.revision, often set in AssemblyInfo.cs, sometimes mixed with wildcard auto increment, sometimes duplicated …
Read Blog Post
Versioning stays invisible right up to the point when it fails. A package has to be reissued, a support case depends on one exact binary, or staging and production turn out to run artifacts from the same commit that do …
Read Blog Post
Publishing NuGet packages has traditionally required one uncomfortable compromise: a long-lived API key had to exist somewhere in the delivery pipeline. Even when that secret was stored in a secure CI system, the model …
Read Blog Post
Auditing is becoming increasingly important in the everyday life of a developer; however, until now there was no particularly good way in .NET - even the lock file still has its deficiencies. You had to rely on …
Read Blog Post.NET now has a very powerful CLI that can also handle NuGet packages very well. But one important feature is missing: check if there are package updates.
Read Blog Post
Kaum ein wirkliches Projekt - sei es im Bereich von .NET, Angular, Node, Java oder anderen Sprachen - kommen heutzutage ohne externe Abhängigkeiten aus.
Read Blog Post