Is it possible to set a shared folder for DLLs with relative processing in Visual Studio 2008?
I am using Team Foundation as a source control for a solution with eight C # projects. To ensure decoupling and stability, I only included dependencies between the project and their tests.
I would like to create a shared folder where compiled libraries and external tools can be placed and shared to solve all projects. The problem is that Solution Packs appear to be virtual and even if they weren't there are still a few other issues such as relative movement and updating of DLLs in the TFS control source.
So my question is, is it possible to create a shared folder containing libraries that all projects in the solution can reference with a relative path and still be able to manage TFS?
Thanks in advance!
source to share
I don't know about TFS, but whenever I add third party libraries for a VS solution for source control, I usually do it in the solution folder.
+-- MySolution
| // The solution is in source control
|
+-- MyProject1
| |
| +-- Project and source code files for a specific project
|
+-- MyProject1.Test
| |
| +-- Test files for MyProject1
|
+-- Third Party
| |
| +-- Library dll are stored here.
|
|
+-- Solution files, more project folders, user settings (user settings are not in source control) etc…
When you specify third party libraries, they must be linked in a relative path. The only way to check this is to open the * proj file and look under the dependency tags if the corresponding library is linked to a relative path rather than an absolute one.
To add libraries to the original control, you simply add the third party folder. Since I am not using TFS, I am not sure if this will fix this setting (I am using Subversion or Mercurial as the source of control and they work well).
source to share