Not really sure which one is worse..... First some background, and I will try to keep it simple....
I have two projects in a solution, A and B where A references B as a project reference in the same solution. Now, we also have the output for the projects pointing to the same assemblies folder(Server Assemblies below) because there is a third project C that references A&B as a file reference.
In case it helps, here is the folder structure for these projects:
Client
Assemblies
Project C
Server
Assemblies
Two Projects (solution is here)
ProjectA
ProjectB
So now the knowledge base article that shed some light on our problem: http://support.microsoft.com/default.aspx?scid=kb;en-us;313512
Title: BUG: "Could Not Copy Temporary Files to the Output Directory" Error Message When You Build a Solution That Contains Multiple Projects
Cause: This problem may occur when one of the assemblies that you compile is larger than 64 kilobytes (KB) and the following conditions is true: Your solution contains projects that are compiled to the same output folder.
Now, our problem is because we have the output directory of projects A&B pointing to the Server/Assemblies folder and our thought there was it would make our file references from ProjectC easier. We read a VSS article that mentioned not to check in the debug/release folders, but we see a need to check in the assemblies at some point so that projects that do file references can work when you “pull latest”. We want to pull the latest on Server/Assemblies, Client(recursively) and have things run for the projects in the client folder.
What I was wondering though is this, how would others structure their projects and how does it impact your VSS structure and build/development processes?
Thanks