In our factory we build extensions for Microsoft server products like SharePoint, Biztalk, XRM etc. In building these extensions we need to reference assemblies of the server products. Currently we provide a folder with these assemblies per server product,
and package these folders with our factory. This means we include a folder with SharePoint 2010 assemblies that is 57 MB! We take this approach because we don't want references to assemblies outside our influence. For example if we would reference SharePoint
assemblies in the folder C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI, it is possible that on another developer machine or the build server SharePoint is installed in another location. Or that we want to compile on a build
server where SharePoint isn't even installed!
We see new possibilities with NuGet, although not with all the assemblies in the
lib folder because then they would all be referenced, or we could use Chocolatey to solve this issue. Any ideas on this?