I want to set up a two separate builds. One for a library, that builds and versions the assembly. My second project will depend on the dll created by the first project.
How do I get the versioned dll from it's project into the second project's workspace to be used in that build?
At the moment you would need to copy the dll to a network share. Dependencies is a feature we are working on for a future update.
Back in the Final Builder Server 7 days, I had a Final Builder Project that would essentially push shared libraries into many other software projects source control by storing all the libraries in the following folder structure.
/lib/SourceCompany/LibraryName.$Build.Version$/*
In my distribution project (Final Builder), I had a prompt that would select the version of the library that I was going to push to the code repositories of the other projects. This way I could coordinate where the library was being used and not break existing software builds. If the project wanted to upgrade the latest edition of a library component they could change that in there software solution, but referencing the newer edition of the library.
When a developer Sync’d there source code with the “Master” repo they got the new library editions and could make a decision on when to implement.
Another option is to use nuget, you can use a network folder as a nuget feed, it doesn’t provide the same level of security and separation as a full nuget server but it is an option. We are working on a Nuget Server module for Continua CI, which will support multiple nuget feeds and security etc.
Got to say I’m heading down the nugget path with internal libraries, as Vincent recommends. There is an open source server implementation @ http://docs.nuget.org/docs/contribute/setting-up-a-local-gallery