Session on different packaging technologies used in a typical development pipeline

1. Packages as the first choice when
deploying – how?
MATTEO EMILI
MICROSOFT MVP – VISUAL STUDIO AND DEVELOPMENT TECHNOLOGIES
MATTEO.EMILI@LIVE.COM || HTTP://MATTVSTS.BLOGSPOT.COM || @MATTVSTS

2. If you need to send something, what would you do?
Pictures from commons.wikimedia.org

3. You definitely consume packages already

4. You already have all the tools you need to create packages!
NuGet?
npm?
ProGet/Artifactory/MyGet?

5. All you need is a Continuous Integration server

6. Build your packages
DEMO

7. Are you saying I can package everything?
Yes*.
* = except for infrastructure, which can be prepared but not in a package.

8. Can I use the same technology for everything?
No.Don’t*.
* = except if you use Octopus Deploy

9. PACKAGES FOR TOOLS AND LIBRARIES
• NuGet, npm, Bower, OneGet
• Interactively consumed by another tool
• Easily replaceable, but they require specific
effort to create
• Immediate logging visibility
• Not meant to be used outside their hosting
environment
PACKAGES FOR APPLICATION DEPLOYMENT
• MSDeploy, *.war, ClickOnce, MSI, Chocolatey
• Consumed in unattended fashion or
interactively by an user
• No creation overhead – it is just an output
format
• Can be tricky to troubleshoot if not setup
correctly
• They aren’t limited to an environment

10. Dealing with Application Deployment
DEMO

11. SemVer
The only way of avoiding dependency hell

12. 1. Major
2.
35
Minor
Patch
Breaking change
Backward-compatible new feature
Backward-compatible bugfix
-ci Tag Additional identifier (pre-release)
1.2.35-ci
Semver.org

13. Any question left?

14. Thanks!