[Original] Use VSS to efficiently manage project DLL

I. Introduction

In the actual project development process, most people will use VSS to manage the project.CodeFile and other resources, we can put all the third-party DLL used in the solution to a fixed folder under a project under the solution, multiple other projects reference the DLL in this folder, so that VSS can be used to manage the DLL of the project. However, this solution is not reasonable:

1. There are multiple projects under a solution. If multiple projects reference the same DLL, the folder dedicated to storing the DLL should be placed under the same directory as the solution (that is,. sln files are in the same directory), instead of placing one project in multiple projects for reference by multiple other projects, so how to put the folder in the same directory as the solution file into VSS for management?

2. In team development, after obtaining the solution and project files from VSS for the first time, other team members have to manually reference all the DLL files so that the Code obtained from VSS can be compiled, is there a way to put the reference relationship between the project and the DLL in VSS for unified management?

 

Ii. Solution

1. A team member is responsible for managing third-party DLL in a team project.

2. Open Vs and create a new "blank solution" named "solutiontest", and select "addSource codeManagement ",:

3. Create a "library" folder in the directory at the same level as the solution file to store the DLL, and copy the third-party DLL used by the project to the library directory ,:

4. Create a new library "solution folder" with the same name in the solution ",:

5. Add the DLL under "library" on the physical disk to the "solution folder" under the solution by adding "existing items ,:

6. Add references to these DLL files in the project that needs to be used, compile the entire program, and recursively check the solution to VSS.

7. After obtaining the latest version from VSS, other team members can directly compile and use it to add DLL references to each project again.

8. If the referenced third-party dll has a new version, you should first check out the DLL from VSS and then open the physical library folder, use a new version of DLL to physically replace the old version of DLL and then check it into VSS. Other team members can directly obtain the latest version.

9. To delete a DLL, right-click the DLL in Vs and choose Delete.

 

Iii. Conclusion

I am also annoyed about how to efficiently manage DLL in my actual project. After many Google attempts, I finally found a better solution, this blog post is available only for sharing with others.

If you have any problems, please correct them.

 

Technorati labels: VSS, source code manager, VSS management DLL, DLL, and VSS efficient management DLL