Do you share code using packages? (Binary and source sharing)
  v4.0 Posted at 21/03/2018 9:32 AM by Tiago Araujo

Devs need a way of sharing and consuming the source code or binaries. 

VSTS is the best home to put it and share it across their organization because: 

  • it caches your packages
  • it's a centralized place for your packages
  • it's constantly evolving (some really cool features are coming...check the video below)

Sharing source or binaries via File Shares or Version Control

Bad example

​Sharing source or binaries via 3rd party tools like ProGet, MyGet

OK example​​

Sharing source or binaries via packages created using VSTS Team Build

Good example
Figure: Start from https://marketplace.visualstudio.com/items?itemName=ms.feed
VSTS is about to add benefits like Component Governance, which allows policies to be set over who can and cannot use the source or binaries E.g. Licensing (MIT might be ok and GPL not ok), security - in development

Good example: Sharing source or binaries via packages created using Sonatype Nexus.
Already supports Component Governance

Additional info

  • At 2:50 Mario Rodriguez talks about the bad ways customers share code
  • At 6:30 Mario explains to Danijel Malik how VSTS helps with the nasty problem of Diamond Dependencies (aka Binary Consumption Hell)   (E.g. That's when devs are trying to get the new version of say Newtonsoft v1.9 in all projects, but one at a time)

Related rules

    Do you feel this rule needs an update?

    If you want to be notified when this rule is updated, please enter your email address:


    Note: Social Media login for Yotpo is not working in IE or Safari, please use Chrome. We are waiting for Yotpo to fix it.