第三方DLL的版本控制的地点为.NET项目 [英] Location of Third Party Dll's in Version Control for .NET Project

问题描述

什么是理想的位置（目录）的一个版本控制系统，以检查第三方参考DLL的一个.NET项目。通常，我所见到的大多数人把他们在垃圾桶，以便运行时可以自动拾取这些文件。然而就是正确的道路要走。

What would be the ideal location (directory) to check in Third Party Reference Dll's for a .NET Project in a version control system. Typically i have seen most people to put them under bin, so that the runtime can automatically pickup these files. However is that the right way to go.

我本来想有平行于斌叫LIB其中将包含所有的第三方DLL的一个单独的目录，但是这需要更改应用程序配置文件，这样的lib目录拾起运行时间。我的想法在这里是lib目录将包含第三方DLL的，而仓将包含项目的二进制文件（可能是DLL或EXE）

I originally wanted to have a separate directory which is parallel to bin called lib which will contain all third party Dll's , but this needs changes to the applications config file so that the lib directory is picked up by the run time. My idea over here is that lib will contain third party dll's while bin will contain the projects Binary (could be Dll or Exe)

什么是preferred方式，在浓度在版本控制的位置，而不仅仅是物理文件系统。

What is the preferred way, The concentration over is the location in the Version Control and not just the Physical File System.

推荐答案

我们使用下面的目录结构（更容易获得信息的在我的博客）：

We use the following directory structure (more details available on my blog):

Solution\
  Libraries\
    third-party DLLs here
  Source\
    Project1\
    Project2\

每个项目引用（使用Add Reference对话框中的浏览选项卡）中的库文件夹中的程序集。这些被自动复制到每一个项目的bin文件夹在编译时。 （库文件夹，当然，致力版本控制。）

Each project references (using the "Browse" tab in the Add Reference dialog) the assemblies in the "Libraries" folder. These are automatically copied to each project's "bin" folder at compile time. (The "Libraries" folder is, of course, committed to version control.)

这篇关于第三方DLL的版本控制的地点为.NET项目的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！