# Library Project

**URL:** https://www.finalbuilder.com/forums/t/library-project/5026
**Category:** Discussion
**Created:** [July 31, 2013, 4:59am UTC](https://www.finalbuilder.com/forums/t/library-project/5026 "2013-07-31T04:59:02Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![doogieh](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/d/3bc359/32.png) [@doogieh](https://www.finalbuilder.com/forums/u/doogieh)
#### Post date: [July 31, 2013, 4:59am UTC](https://www.finalbuilder.com/forums/t/library-project/5026/1 "2013-07-31T04:59:02Z")

</div>

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?

---

<div class="post-metadata">

### Author: ![Vincent](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/vincent/32/938_2.png) [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)
#### Post date: [August 1, 2013, 12:15pm UTC](https://www.finalbuilder.com/forums/t/library-project/5026/2 "2013-08-01T12:15:05Z")

</div>

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.

---

<div class="post-metadata">

### Author: ![deleted\_user](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/deleted_user/32/937_2.png) [@deleted\_user](https://www.finalbuilder.com/forums/u/deleted_user)
#### Post date: [August 2, 2013, 7:50am UTC](https://www.finalbuilder.com/forums/t/library-project/5026/3 "2013-08-02T07:50:53Z")

</div>

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.

---

<div class="post-metadata">

### Author: ![Vincent](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/vincent/32/938_2.png) [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)
#### Post date: [August 2, 2013, 8:34am UTC](https://www.finalbuilder.com/forums/t/library-project/5026/4 "2013-08-02T08:34:03Z")

</div>

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.

---

<div class="post-metadata">

### Author: ![deleted\_user](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/deleted_user/32/937_2.png) [@deleted\_user](https://www.finalbuilder.com/forums/u/deleted_user)
#### Post date: [August 2, 2013, 9:26am UTC](https://www.finalbuilder.com/forums/t/library-project/5026/5 "2013-08-02T09:26:52Z")

</div>

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](http://docs.nuget.org/docs/contribute/setting-up-a-local-gallery)
