Code Sharing Part 2: Automatic Semantic Versioning of NuGet Deploys
How to automatically incorporate semantic version information into NuGet libraries during building, packaging, and publishing of .Net libraries to private NuGet feeds.
How to automatically incorporate semantic version information into NuGet libraries during building, packaging, and publishing of .Net libraries to private NuGet feeds.
If you've ever tried to share code like an API proxy, math calculations, or validation logic between multiple projects, you'll know there are many options. In this post I'll summarize the most common, then dig into the most versatile for .Net projects: private NuGet feeds
I just posted Episode 18 of Code Hour. In this show I demonstrate how to build a Printed Circuit Board (PCB) from prototype, to design, to manufacture.
A couple of months ago calculating code coverage on the command line was quite challenging in ASP.Net Core. Fortunately, as of last month and Visual Studio 15.8, generating the metric is easy.
In this post I'll summarize what code coverage is, how it can be abused, but also how it can be leveraged to gently increase design and architecture quality, reduce bug regressions, and provide verifiable documentation.