TFS 区域，最佳定义和配置 [英] TFS Areas, Optimal Definition and Configuration

问题描述

最近迁移到 TFS 2010 后，我想知道区域的最佳或最广泛接受的定义或配置是什么?

Having recently migrated to TFS 2010 I was wondering what the best or most widely accepted definition or configuration is for an Area?

我在网上能找到的唯一有用的文章是 这个 并且是我认为是正确的.然而，这让我开始思考以下任何一项是否确实被更广泛地接受.

The only useful article I can find online is this one and is what I would have assumed to be correct. However it got me thinking if any of the following is indeed more widely accepted.

• 按业务功能划分的区域
• 技术领域
• 按系统层划分的区域
• 按物理或地理位置划分的区域

推荐答案

这实际上取决于您正在构建的产品/项目，我想它是作为通用占位符提供的，可以从上下文中获取其含义团队和团队任务.
我可以想象，在总体上忽略它的项目也将是一个完全可以接受的解决方案.

我们最初的 TeamProject 结构实际上确实忽略了我们构建的旗舰产品的区域团队收藏.这导致了报告噩梦，因为我们需要在平台级别 (TeamCollection) 上使用它，而不是它的一个独特部分 (Team Project).当我们意识到问题时，我们开始搜索&找到 这篇 文章，这让我们改变了方向:我们现在在一个团队项目中使用 TFS 区域 &找到最适合我们情况的方法.
在我们的宇宙中区域 = 平台内的独特发布线.

It really depends on the product/project you 're building, I suppose it was made available as a general-purpose placeholder which can get its meaning from the context of the team & the team mission.
I can imagine projects, where ignoring it on the grand total, would also be a perfectly acceptable solution.

Our initial TeamProject structure in fact did ignore Areas for our flagship product we construct in a Team Collection. This resulted in a reporting nightmare, since we needed it on a platform-level (TeamCollection), rather than a distinct part of it (Team Project). When we realized the problem, we went searching & found this article, which made us change course: we are now using TFS Areas within one single Team Project & found what fitted best to our situation.
In our universe Area = a distinct release line within the platform.

这篇关于TFS 区域，最佳定义和配置的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！