如何正确地将DLL/程序集检入到TFS/Visual Studio Team Services(以前是VSO) [英] How to properly check in DLLs/assemblies to TFS/Visual Studio Team Services (was VSO)

问题描述

我们有一个项目引用的多个DLL，这些DLL无法通过NuGet获得.从TFS/VSTS中提取解决方案后，每次都要复制DLL文件，这对于不熟悉我们项目的ppl来说是相当繁琐且令人困惑的.

We have several DLLs referenced by a project that are not available through NuGet. Every time one has to copy the DLL file across after pulling the solution from TFS/VSTS, which is quite tedious and confusing for ppl not familiar with our projects.

有没有一种方法可以正确检查DLL到TFS/VSTS中?显然，我们可以在解决方案中包含BIN文件夹，但这是正确的做法吗?

Is there a way to properly check the DLLs in to TFS/VSTS? Obviously we can include the BIN folder in the solution but is that the right thing to do?

推荐答案

在某些情况下，有一个名为"libs"或"libraries"的文件夹很有用，例如，其中包含项目编译所需的所有程序集并运行.因此，您可以签入此文件夹.在每个项目中，您都需要引用此处包含的dll(Visual Studio使用相对路径自动保存路径). 包括"bin"文件夹是不正确的方法，因为如果开发人员在Visual Studio中执行清理解决方案"，它将清理此文件夹.

In some scenarios it's useful to have a folder named "libs", or "libraries", for example, that contains all the assemblies required by your projects to compile and run. So you can check-in this folder. In each project you need to reference the dll contained here (Visual Studio automatically save the path using relative path). Include the "bin" folder is not the right way, because if a developer performs a "Clean solution" in Visual Studio, it clean this folder.

这篇关于如何正确地将DLL/程序集检入到TFS/Visual Studio Team Services(以前是VSO)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！