Class Libraries, Shadow Folders, Bin Folder

TampaWebDevelopment · Post by **TampaWebDevelopment** » Fri Aug 31, 2007 1:20 pm

I have a solution. Within that solution, I have one web project and 4 class library projects. The web project references the class libraries. When I build the solution, the dll files from the class libraries are correctly getting added to my web project's bin folder. I have a shadown folder setup on the vault server to my development website's directory. So, when I check-in files, the files are moved to the shadow folder and the development websites (dev.website.com) is updated instantly. The problem that I am having is the dll files from the class libraries are not actually getting added to the source controlled version of the website, thus they are not copied to the shadow folder. If you look, the class library project's dll files are not getting a lock next to them in the bin folder of the web project. I am sure this is by design so that each time a build happens, the files don't have to be checked out, etc. How can I correctly set this up so that the valut adds a copy of the class library dll files to the shadow folder?

Beth · Post by **Beth** » Fri Aug 31, 2007 1:59 pm

Can you tell me which version of Vault you are using? If you're using 4.x, can you tell me if you are using the VS 2003 compatible client or the VS 2005 client?

Visual Studio isn't supposed to be adding /bin folders or .dlls to source control. A lot of people have spoken to Visual Studio about that, so if it's not happening to you, you actually have correct behavior.

If you did add them in, then your build would fail unless you checked those .dlls out each time, because they would be made read-only.

If you wanted them in anyway, you could do that manually, but you have to check them out each time to build.

Another option would be to have a build performed right at the server when files are updated.

TampaWebDevelopment · Post by **TampaWebDevelopment** » Fri Aug 31, 2007 2:13 pm

Beth wrote:Can you tell me which version of Vault you are using? If you're using 4.x, can you tell me if you are using the VS 2003 compatible client or the VS 2005 client?

Visual Studio isn't supposed to be adding /bin folders or .dlls to source control. A lot of people have spoken to Visual Studio about that, so if it's not happening to you, you actually have correct behavior.

If you did add them in, then your build would fail unless you checked those .dlls out each time, because they would be made read-only.

If you wanted them in anyway, you could do that manually, but you have to check them out each time to build.

Another option would be to have a build performed right at the server when files are updated.

I am currently using version 3.5 because one of the companies that I work for hasn't upgraded yet. When I reference a 3rd party library that is just a DLL file, that file is added to the bin folder and IS added to source control. The items that are NOT added to source control are the output files (dlls) of a referenced project. So, I agree that it does have the correct behavior. But, does that mean that I can not get the project output of a referenced class library added to the shadow folder?

Beth · Post by **Beth** » Fri Aug 31, 2007 2:48 pm

If you added it manually, it will propagate to the shadow folder. You would then have to check them out when you build, because they get changed.

If you are adding an entire folder, then will want to go to the Admin tool to remove the file and folder exclusions for what you want to add.