I really dig the idea of NuGet packages being produced and published by an automated CI build system. While we’ve all been doing CI for years, standardized packaging and distribution options in .NET for large and complex project trees are still fairly few in number. For the most part, build systems spit out .DLLs and .EXEs, perhaps a .ZIP, and occasionally an .MSI file capable of bootstrapping a production server or a developer workstation in more sophisticated examples. It’s that last bit where NuGet rocks — the framework provides an easy peasy way to publish and distribute your libraries to developer workstations, and eventually into the builds of projects that use them. Note: Scott Hanselman recently wrote a blog post describing a very similar CI build system — [...]