TFS 磁盘结构 - 和“添加新文件夹”与“添加溶液”相比

发布于 2024-09-03 06:41:46 字数 1149 浏览 3 评论 0原文

我们的组织最近设置了 TFS 2008 供我们使用。我有一个可以练习的 TeamProject。

为了稍微简化一下，我们之前在磁盘上组织代码的方式如下：

-EC
  - Main
     - Database
         - someScript1.sql 
         - someScript2.sql 
     - Documents
         - ReleaseNotes_V1.doc 
     - Source
        - Common
           - Company.EC.Common.Biztalk.Artifacts [folder]
           - Company.EC.Common.BizTalk.Components [folder]
           - Company.EC.Common.Biztalk.Deployment  [folder]
           - Company.EC.BookTransfer.BizTalk.sln
        - BookTransfer
           - Company.EC.BookTransfer.BizTalk.Artifacts [folder]
           - Company.EC.BookTransfer.BizTalk.Components [folder]
           - Company.EC.BookTransfer.BizTalk.Components.UnitTest [folder]
           - Company.EC.BookTransfer.BizTalk.Deployment [folder]
           - Company.EC.BookTransfer.BizTalk.sln

我正在尝试决定，是否要签入整个 c:\EC 目录？或者我想打开每个解决方案并签入。各自的优点和缺点是什么？似乎通过执行“添加文件/文件夹”选项，我可以立即检查所有内容，并且它将与磁盘结构匹配。

看起来，如果我单独签入每个解决方案，则会在我的工作区中创建另一个工作文件夹。我想如果我通过“添加文件/文件夹”签入，我将拥有一个工作区，那会更好。

但我看到的大多数书籍和示例都讨论了检查项目和解决方案。

PS 我知道我需要根据分支/合并指南向我的磁盘结构添加更多内容，但这不是我在这里问的问题。

谢谢，尼尔·沃尔特斯

原文

Our organization recently got TFS 2008 set up ready for our use. I have a practice TeamProject available to play with.

To simplify slightly, we previous organized our code on disk like this:

-EC
  - Main
     - Database
         - someScript1.sql 
         - someScript2.sql 
     - Documents
         - ReleaseNotes_V1.doc 
     - Source
        - Common
           - Company.EC.Common.Biztalk.Artifacts [folder]
           - Company.EC.Common.BizTalk.Components [folder]
           - Company.EC.Common.Biztalk.Deployment  [folder]
           - Company.EC.BookTransfer.BizTalk.sln
        - BookTransfer
           - Company.EC.BookTransfer.BizTalk.Artifacts [folder]
           - Company.EC.BookTransfer.BizTalk.Components [folder]
           - Company.EC.BookTransfer.BizTalk.Components.UnitTest [folder]
           - Company.EC.BookTransfer.BizTalk.Deployment [folder]
           - Company.EC.BookTransfer.BizTalk.sln

I'm trying to decide, do I want to check in the entire c:\EC directory?
Or do I want to open each solution and checkin. What are the pros and cons of each?
It seems like by doing the "Add Files/Folder" option, I could check in everything at once and it would match the disk structure.

It also looks like that if I check in each solution separately, that creates another working folder in my Workspace. I think if I check in by "add files/folder", I will have one workspace and that would be better.

But most of the books and samples I see talk about checking in projects and solutions.

P.S. I know I need to add more to my disk structure in accordance with the Branch/Merge guidelines, but that is not the question I'm asking here.

Thanks,
Neal Walters

分享到QQ

分享到微博