title: How to provide non-deployed dependencies to a build service?
body: <p>Some times ago I asked the question about <a href="https://stackoverflow.com/questions/6607077/how-to-integrate-an-application-using-dependencies-on-a-build-server">how to integrate an application using dependencies on a build server</a> and I had quite satisfying answers. Today I am facing a different case. For a project I have to use <strong>non-redistribuable</strong> depedencies (RDL object model for SSRS). It means that out-of-the-box, these assemblies are not made to be deployed for development purpose. But somehow, I need to...</p>
  
  <p>My first guess was to <strong>publish them in the GAC</strong>. Fine, it worked and the build server was able to compile the project smoothly. But then I realised that <strong>it broke some applications</strong> like the Report Server and the Report Builder (probably it would also break BIDS). So publishing in the GAC is definitely not a decent solution.</p>
  
  <p>My second guess was to <strong>check the assemblies in source control</strong>. Well, it could work if I had only 2 assemblies for an amount of about 1MB. But here it is <strong>23 assemblies and 29MB</strong> I have to check in, so it is definitely not suitable either.</p>
  
  <p>I don't know much about MSBuild targets and maybe it could be a solution but I really have no idea on how to use it. I have been scratching my head hard and now I have to chose between breaking my builds or breaking my services!</p>