Each month, we bring you the insiders view into Visual Studio Team Services – how the product is developed, how we dogfood it and use it every day, who are the people behind it and tips and tricks on becoming a power user This month,
This is the third and final post in a series covering strategies for versioning a NuGet package. If you missed part 1 or part 2, you should read those first. Today’s post walks through a specific workflow that Git users could adopt,
This is part 2 in a series of blog posts covering strategies for versioning a NuGet package. If you missed part 1, pick it up here. Today’s post talks about future improvements we’d like to make to the versioning and releasing flows.
On the Package Management team, we’re frequently asked how to think about versioning packages. Conceptually, it’s simple: NuGet (like many package managers) prefers semantic versioning (SemVer), which describes a release in terms of its backwards-compatibility with the last release. But for teams that have adopted continuous delivery,
Since we launched Package Management Public Preview last November, your response has been fantastic. Thank you to everyone who’s installed our extension, published a NuGet package, or sent us feedback. As the sunshine starts to return to Seattle, it’s time for some spring cleaning.
Für diese Internetseite verwenden wir Cookies für folgende Funktionen:
The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.