This document discusses using an automated Nuget system to manage dependencies and speed up builds across multiple repositories for a software project. Key points: 1) Nuget is good for managing dependencies but the project needs to keep dependencies consistent and automate updates across their build chain involving multiple components. 2) Two potential solutions are explored: semantic versioning and automating Nuget updates. The document focuses on automating Nuget to make builds faster, dependency resolution easier, and reduce unwanted changes compared to using vanilla Nuget. 3) A demo of their customized Nuget system is mentioned, highlighting it has a graphical user interface that makes managing dependencies easier than command line tools.

1. Nuget Updater

2. Nuget is really good at
Dependencies which are:
Static
External
Rarely-updated
Shallow

3. For us, Nuget is pretty good at
Creating easy local builds
- only have to check out one repository
- dependencies are specified explicitly – more reliable
Speeding up Teamcity builds
- no snapshot dependencies
- each build can start immediately
- fewer artifacts to download

4. The state of Compare
Shared Utils
Backup Reader
AST Parser
Compare Engine
SQL Tools UI
Data Compare Engine
SQL Compare UI
Installer
Migrations v2

5. The state of Compare (reality)
We have to keep the Shared Utils version consistent across the whole build chain
Shared Utils
Every single thing in the entire universe

6. Tradeoffs
While individual builds are fast ..
Shared Utils
Backup Reader
AST Parser
Compare Engine
SQL Tools UI
Data Compare Engine
SQL Compare UI
Installer
Migrations v2
Time from Engine to UI to installer is longer
- Packages have to be manually updated at each step

7. Two possible solutions
Semantic versioning
- drop any compatible version of the engine into a UI build
- going to investigate this more in the future (see GrahamH)
Automate NuGet
- this is what we’re trying

8. Why not vanilla nuget?
We can
- be faster to use (choice of UI vs commandline)
- be easier to automate
- have better dependency resolution (at least compared to nuget v2)
- run across multiple repositories
- have fewer unwanted changes

9. Fewer unwanted changes
Normalnuget
- Find and replace csproj references
- Add specificversion=False
- Remove private=True
- Remove aliases
- Add additional content from package
- Add app.config file
- Add assembly binding redirects to
app.config
- and so on ..
Us
- Find and replace the right version
numbers

10. Demo
Commandlines are boring
But we have a shiny new CEF UI!