Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Visug - organize your chickens - nuget for the enterprise


Published on

Published in: Technology
  • Login to see the comments

  • Be the first to like this

Visug - organize your chickens - nuget for the enterprise

  1. 1.
  2. 2. Organize your chickens NuGet for the Enterprise
  3. 3. Who are we?• Maarten Balliauw• Antwerp, Belgium•• Focus on web – ASP.NET, ASP.NET MVC, PHP, Azure, … – MVP Windows Azure (formerly ASP.NET)•• @maartenballiauw
  4. 4. Who are we?• Xavier Decoster• Antwerp, Belgium•• Focus on web/ALM – Visual Studio, TFS, Scrum, ... – Silverlight, ASP.NET, ASP.NET MVC, …•• @xavierdecoster
  5. 5. Agenda• Chickens?• NuGet• Scenarios – Host your own NuGet repository – Continuous (Package) Integration – (Ab)using NuGet• Conclusion
  6. 6. Welcome to Dependency Hell“A term for the frustration of software users who have installedsoftware packages which have dependencies on specificversions of other software packages.” Source: Wikipedia
  7. 7. Cause and Effect• Reinventing the wheel – We don’t need that dependency – “If they can do it, we can do it, but better”  What happened to reuse of components?• Marketing does the versioning – People are waiting for v2 to buy – Let’s call it v4 Platform Update SP3 November Edition KB2348063 RTW Refresh  We lost ownership of AssemblyVersion ?
  8. 8. Package Management• NuGet to the Rescue! “NuGet is a Visual Studio extension that makes it easy to install and update open source libraries and tools in Visual Studio.”• Simple concept – Find Packages – (Re)Use Packages – Produce Packages
  9. 9. Semantic Versioning• Think about your versioning! ( Major Breaking changes Minor Backwards compatible API additions/changes Patch Bugfixes not affecting the API – Always specify lowerbound – Use a version range (lowerbound + upperbound) when versioning of package you depend on is messed up
  10. 10. Advanced usage scenarios• Host your own NuGet repository• Continuous (Package) Integration• (Ab)using NuGet
  12. 12. Hosting your own repository• NuGet = public feed – Privacy – Intellectual property• NuGet maintained by package authors – Author removes v1.0.45 and you depend on it
  13. 13. Solutions• Folder / File share• Orchard Gallery (or NuGet Gallery)• NuGet.Server package• MyGet
  14. 14. Install-Package NuGet.ServerNUGET.SERVER DEMO
  15. 15. NuGet.Server limitations• Only 1 feed per installation• No UI: up to you to build it• No granular security: only 1 API-key for entire feed• Conclusion: requires you to develop if you want something more useful
  16. 16. Meet MyGet•• NaaS – Register and off you go! (no dev)• Supports Enterprise scenarios – Granular security – Package mirroring
  17. 17. Log in to and get startedMYGET DEMO
  19. 19. Typical source control...• Contains /References (if you are lucky) – ...and also Project/_bin_deployable_assemblies – ...and also /References/old – ...and also /..././../.././References• Usually references GAC-ed assemblies
  20. 20. Dependencies• Software has dependencies. Deal with it.• But are those YOUR intellectual property? – YOUR reason to build software? – YOUR product?• No. They are dependencies. And they don’t belong in source control.
  21. 21. Continuous (Package) Integration• Can I get rid of all these referenced assemblies duplicated all-over my source control system? Yes!• Do I need to install and maintain NuGet on all my build agents? No!
  22. 22. Organize your build chickens!NUGETPOWERTOOLS DEMO
  23. 23. 3rd parties don’t belong in your SCM• Replace them with NuGet packages• Commit packages/repositories.config files• Use NuGetPowerTools Enable- PackageRestore• Set package-source location(s) (NuGet.settings.targets in $(SolutionDir).nuget folder)
  24. 24. Problem!• NuGet feed is subject to change... – PackageSource msbuild property to the rescue• Now what... – Host your own feed and mirror packages – Or use MyGet for that 
  25. 25. Organize your chickens• Feed structuring – Scoped by quality: Build, QA, Production, … – Scoped by audience: public, restricted access – Other: • Scoped by product version, milestone… • Scoped by target platform
  26. 26. (AB)USING NUGET
  27. 27. Guidance• Publishing a package brings great responsibility – Breaking changes in your packages should be versioned accordingly! – Consumers might choose to no longer consume any packages you published
  28. 28. Guidance• Package Integration ≠ Integration Testing – CI builds reflect output of source control input – Same input always produces same output  Do not auto-update packages during automated builds
  29. 29. (Ab)using NuGet?• Change of perspective NuGet is a package manager NuGet is a protocol for distributing packages
  30. 30. Scaffolding, CmdLets, Plug-ins, …EXTENDING NUGET
  31. 31. Automate deployments• Build results in .nupkg• Octopus deploys to its tentacles – Test tentacles – Staging tentacles – Production tentacles•
  32. 32.
  33. 33. Chocolatey• NuGet – developer library packages• Chocolatey – applications and tools packager – “yum” or “apt-get” for Windows•
  34. 34. NuGet desertCHOCOLATEY DEMO
  35. 35. Orchard / WebMatrix / …• NuGet not bound to VS• Orchard CMS: modules & themes• WebMatrix: install page helpers on the fly• Your app: offer plugins through a repo
  36. 36. CONCLUSION
  37. 37. Conclusion• Dependencies & people are chickens Deal with them! NuGet can help• Set up your own NuGet repository for various reasons• Continuous package integration• NuGet is a package manager NuGet is a protocol
  38. 38. @maartenballiauw @xavierdecosterAny questions?THANK YOU!