Download - Using nu get the way you should svcc
![Page 1: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/1.jpg)
Using NuGetthe way you shouldMaarten Balliauw@maartenballiauw
![Page 2: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/2.jpg)
Who am I?
• Maarten Balliauw• Antwerp, Belgium• Developer Advocate, JetBrains• Founder, MyGet• AZUG• Focus on web• Big passion: Azure• http://blog.maartenballiauw.be • @maartenballiauw Shameless self promotion: Pro NuGet - http://amzn.to/pronuget2
![Page 3: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/3.jpg)
Agenda
• NuGet• File | New Project…• The state of NuGet• Every project is a package• Creating packages• Distributing packages• Consuming packages
![Page 4: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/4.jpg)
NuGet
![Page 5: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/5.jpg)
A brief NuGet introduction...
• Package management system for .NET• Visual Studio extension, command line, console
• Simplifies incorporating 3rd party libraries• Developer focused• Free, open source
• Use packages from the official feed• Publish your own packages• Create & use your own feed
![Page 6: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/6.jpg)
File | New Project...
![Page 7: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/7.jpg)
DemoFile | New Project...
![Page 8: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/8.jpg)
That was trouble!
•Dependencies on NuGet packages•Dependencies on projects•Dependencies on file system layout•Breaking changes in dependencies
Dependency hell
![Page 9: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/9.jpg)
“Dependencies, also in real life, are trouble. Have you ever had to depend on a plumber showing up?”- Maarten Balliauw
![Page 10: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/10.jpg)
Dependencies before NuGet
•Projects in solution•Reference in-house projects:
• Either the assemblies (typically unversioned / all 1.0.0.0)
• Either the actual project / linked files (unversioned by design)
•Reference third party assemblies (e.g. JSON.NET)
![Page 11: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/11.jpg)
Dependencies with NuGet
•Projects in solution•Reference in-house projects:
• Either the assemblies (typically unversioned / all 1.0.0.0)• Either the actual project / linked files (unversioned by design)
•Reference third party packages (e.g. JSON.NET)• Semantic Versioning to announce breaking changes
(happy times as long as package authors respect that)
![Page 12: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/12.jpg)
The state of NuGet
![Page 13: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/13.jpg)
The state of NuGet
•We are consumers!• Even quite some overconsumption I dare say…
•We sort of know about Semantic Versioning• If the mayor version changes, we’re doomed
•Are we producing?• Some are, e.g. OSS and some companies
•Did we solve our dependency issues?
Where are we, 3 years in?
![Page 14: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/14.jpg)
.NET is late to the party!
•Others have been doing package management for decades• Perl (CPAN.org)• Linux (RPM/YUM/APT-GET/...)• PHP (PEAR, Composer)• Node (npm)• Ruby (Gems)
•We can learn a great deal from these!
![Page 15: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/15.jpg)
What are the others doing?{ "name" : "IniTech.Framework.Formatters", "version" : "1.0.0 ", "author" : "Maarten Balliauw", "bugs" : { "url" : "https://github.com/initech/framework-formatters/issues" }, "description" : "Formatters specific to the IniTech organization.", "homepage" : "https://github.com/initech/framework-formatters", "keywords" : [ "framework", "formatters", "initech" ], "license" : "Proprietary", "main" : "index.js", "repository" : { "type" : "git", "url" : "https://github.com/initech/framework-formatters" }, "scripts" : { "test" : "echo \"Error: no test specified\" && exit 1" }, "dependencies" : { "date-format" : "0.0.2", "format" : "~0.2.1", "moment" : "~2.5.1" }}
![Page 16: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/16.jpg)
What are the others doing?
•Name and version of the project•Dependencies (and version range) of the project
•Every project is a package!• It can have dependencies• It can be depended on
What was in that package.json?
![Page 17: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/17.jpg)
Every project is a package
![Page 18: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/18.jpg)
Supporting componentization
•Every project is a package• Clearly identifyable• Proper Semantic Versioning
•Every project becomes discoverable• Nice description, release notes, ...• Add it to a private feed so developers can find it
•Dependencies (can) stay out of source control•Dependencies are versioned
![Page 19: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/19.jpg)
But… NuGet only has packages.config!
•Nodejs: packages.json•Composer (PHP): composer.json•NuGet:
• packages.config: dependencies• <projectname>.nuspec: package description• NuGet.config: other settings• It’s 2-3 files in our world, but it is all there.
•Let’s become producers!
![Page 20: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/20.jpg)
Creating packages
![Page 21: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/21.jpg)
All we need is one file
•XML file which can be generated• nuget.exe spec• Install-Package NuSpec && Install-Nuspec
•Run nuget.exe pack to create package
<projectname>.nuspec
![Page 22: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/22.jpg)
DemoCreating packages
![Page 23: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/23.jpg)
Think about versioning!
• www.semver.org
• SemVer states intentions• It’s the only way toavoid dependencyversioning hell.But not bullet-proof.
Enforce Explicit Semantic Versioning
Major Breaking changes
Minor Backwards compatible changese.g. API additions
Patch Bugfixes not affecting the API<dependency id="ExamplePackage" version="1.3.2" />
1.0 = 1.0 ≤ x(,1.0] = x ≤ 1.0(,1.0) = x < 1.0[1.0] = x == 1.0(1.0) = invalid(1.0,) = 1.0 < x(1.0,2.0) = 1.0 < x < 2.0[1.0,2.0] = 1.0 ≤ x ≤ 2.0empty = latest version
![Page 24: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/24.jpg)
Distributing packages
![Page 25: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/25.jpg)
Which medium?
• In source control (please don’t)
• Local / network folder (slow > ~50 packages)
• NuGet.Server (slow > ~50 packages)
• NuGet Gallery (clone of www.nuget.org)• MyGet (www.myget.org, SaaS) • ProGet (www.inedo.com/proget)• TeamCity NuGet artifacts (www.jetbrains.com/teamcity)• Sonatype (www.sonatype.com/nexus) • Artifactory (www.jfrog.com)
We will need a “package source” or feed
![Page 26: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/26.jpg)
How do they get there?
•Manual upload•As part of our continuous integration process• All benefits of CI (e.g. testing)• Plus reporting on which packages we are using• Plus publishing packages for consumption
![Page 27: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/27.jpg)
DemoContinuous Integration& Distributing Packages with TeamCity
![Page 28: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/28.jpg)
What did we just see?
•Creating packages using .nuspec•NuGet configuration inheritance•Continuous Integration on TeamCity
• How to run package restore• How to build a package• How to see packages that are being used
•How to consume a package
![Page 29: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/29.jpg)
NuGet configuration inheritance
•Make settings common to projects!• NuGet walks up the directory tree to find NuGet.config files
•Or even push them to developer machines• %AppData%\NuGet\NuGet.config• %ProgramData%\NuGet\Config\*.config• ...
•See http://bit.ly/nuget-config-inheritance •Configure feeds, proxy, credentials, ...
![Page 30: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/30.jpg)
More recommendations…
•Don’t just update blindly• Not everyone respects SemVer…• It would take us back to the original problem
•Don’t autoupdate during builds• Continuous Integration: Same Input = Same Output• Be explicit about versioning
![Page 31: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/31.jpg)
Deploying from NuGet packages
•Using a simple, handcrafted script•Using a tool like OctopusDeploy.com
• Which is even cooler combined with Chocolatey.org
•TeamCity supports various ways of deploying (e.g. WebDeploy)
![Page 32: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/32.jpg)
DemoDeploying packaged applicationswith a handcrafted script
![Page 33: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/33.jpg)
Considerations
•TeamCity internal NuGet feed• Only build artifacts
• No way to add external packages that are being used• May not be a problem for your setup
• But maybe it is: a feed is much like source control for dependencies
• Add dependencies that are being used, NuGet.org, component vendors, ...
• If it is, create your own feed, e.g. MyGet.org
![Page 34: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/34.jpg)
Create a package source / feed
•That’s a cool library! And that one too!• Avoid overconsumption by limiting packages• May not block developers but at least the build will fail
•Your own feed will only contain packages you know• Keep versions under control• Keep licensing under control• Easy way to audit external packages in use
For your team or the entire organization
![Page 35: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/35.jpg)
DemoPushing packages from TeamCity
![Page 36: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/36.jpg)
But I’m using NuGet. It’s broken!!!
•Tied to Visual Studio•Merging sucks (XML merge, yuck!)•Updating fails often•Disk space pollution•Project re-targeting•Pessimistic package version picker / fixed versions
http://blog.nuget.org/20141010/nuget-is-broken.html
![Page 37: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/37.jpg)
DemoASP.NET vNext approach is the way forward!
![Page 38: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/38.jpg)
Conclusions
![Page 39: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/39.jpg)
Conclusions
• NuGet• File | New Project…• The state of NuGet• Every project is a package• Creating packages• Distributing packages• Consuming packages
What have we learned?
![Page 40: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/40.jpg)
“Project references must die. Embrace NuGet by consuming and creating packages. It’s a logical evolution.”- Maarten Balliauw
![Page 41: Using nu get the way you should svcc](https://reader036.vdocument.in/reader036/viewer/2022062706/557dc633d8b42a8a188b542b/html5/thumbnails/41.jpg)
Thank you!http://blog.maartenballiauw.be@maartenballiauwhttp://amzn.to/pronuget2