Semantic Versioning & auto-incremented NuGet package versions
Any NuGet package is uniquely identified by a package ID and a version. If you've been to one of my talks or follow my blog, you know I'm quite a fan of sema...
Any NuGet package is uniquely identified by a package ID and a version. If you've been to one of my talks or follow my blog, you know I'm quite a fan of sema...
Update: This post pre-dates NuGet v2.7 which changed the NuGet package restore flow (it is now by default no longer part of the MSBuild process, but runs b...
As we have reached 1500 NuGet feeds on MyGet for the first time – with some great stuff in our Gallery - we felt it's about time we make it even easier for p...
If you've been in one of my recent talks or follow my blog or Twitter ramblings, you might have noticed I'm quite a fan of adhering to the Semantic Versionin...
I'm really happy I got the opportunity to talk at the Danish Warm Crocodile Conference this week. I loved the enthousiasm and interactivity with the audience...
In order to add some custom post-build steps to a TFS Build process, it usually comes in handy - might sound as a surprise - to get a hold on the produced ou...
I'm usually not the guy who spends too much time looking at the past, but 2012 has been so much fun I can't resist the temptation of summing up what I've enj...
In my post on how to restore packages from a secured feed, I already anticipated an important fix in the upcoming 2.2 release of NuGet to further facilitate ...
One of the most frequently asked questions at MyGet is the following one (we have pending updates to our FAQ section):
Today I noticed a question on StackOverflow that proved I wasn't the only one finding it a little sub-optimal having to update NuGet packages right after cre...