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

查看:22
本文介绍了如何正确检入 DLL/程序集到 TFS/Visual Studio Team Services(是 VSO)的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们有几个 DLL 由项目引用,但无法通过 NuGet 获得.每次从TFS/VSTS中拉出解决方案后都要复制DLL文件,这对于不熟悉我们项目的人来说非常繁琐和混乱.

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屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆