SharePoint 网站的版本控制？
我们同时在 SharePoint 网站上工作。我们必须将它们转移到源代码控制系统上。我们有 VSS 和 TFS。由于 TFS 的可靠性，我们更喜欢 TFS 而不是 VSS。我不知道如何将 SharePoint 网站与 TFS 绑定？它与 SharePoint 站点有点混淆的原因是，并非所有依赖项都在站点中，它可能具有布局、功能等，并且它们部署在站点文件夹之外。如何通过版本控制器（或 TFS）管理 SharePoint 网站的各个部分？
谢谢。
We're working simultaneously on SharePoint sites. We've to move them on a source control system. We've got both VSS and TFS. We'll prefer TFS over VSS because of its reliability. I don't have any idea how to bind a SharePoint site with TFS? The reason it is a bit confused with SharePoint site is not all dependencies are in there in the site it could have Layouts, Features etc. and they are deploy outside the site folder. How could you manage the separate pieces of a SharePoint site through a version controller (or TFS)?
Thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
使用浏览器将内容直接发布到生产环境 - 您可以使用网站集备份来使用生产环境中的最新内容来补充临时和开发服务器。
可部署的解决方案、功能等是向相反的方向推出的：从开发到分阶段再到生产。
这就是 SharePoint 的设计方式：内容和代码以相反的方向流动。仅使用 TFS 存储您的代码。
Content is posted directly to production using the browser - you can use site collection backups to rehydrate staging and development servers with latest content from production.
Deployable solutions, features, etc., are pushed out in the opposite direction: from development to staging to production.
This is the way SharePoint is designed: content and code flow in opposite directions to each other. Use TFS to store your code only.
这是SharePoint开发的问题之一。
我们不在源代码管理中保留任何“内容”，所有内容都是代码，包括我们添加到 _layouts 的所有内容。
内容（内容数据库中的所有内容）仍然是“解决方案”的组成部分。为此，我们使用 SharePoint 中内置的版本控制，并且集成服务器包含可供所有人从中获取副本的源副本。内容的部署方式与代码不同，因此它不包含在构建中。
在某些项目中，这可以通过导出和导入或备份来实现；每个开发人员都会签入解决方案使用的站点的导出，并且可以在其他开发环境上恢复。这将不允许合并并覆盖开发人员自己的内容。
This is one of the problems with SharePoint development.
We don't keep any 'content' in source control, all that goes in there is the code, including everything we add to _layouts.
Content (everything that is in a content database) still is an integral part of 'the solution'. We use the versioning that is built into SharePoint for that and the integration server contains the source copy for all to get copies from. Content doesn't deploy the same way as code so it is not included in builds.
In some projects this may be possible using exports and imports or backups; every developer checks in an export of the site that the solution uses and this can be restored on the other development environments. This won't allow merging and overwrites the developers own content.
ArjanP 和 IrishChieftan 关于代码和工件分离的观点是正确的。应该可以将工件移至 TFS，但不推荐这样做。我正在研究有关 SharePoint 和 TFS 的类似问题，发现这些文章非常有帮助：
Microsoft Office SharePoint Server 2007 中的基于团队的开发
http://msdn.microsoft.com/en-us/library/bb428899.aspx
我们如何进行 SharePoint 开发，包括 TFS 集成？ （MCS 芬兰团队）
http://blogs.msdn.com/vesku/archive/2009/10/25/how-do-we-do-sharepoint-development-include-tfs-integration.aspx
希望这有帮助。
ArjanP and IrishChieftan are correct about the separation of code and artifacts. It is supposed to be possible to move artifacts into TFS but it is not reccommended. I am researching similar issues around SharePoint and TFS and found these articles very helpful:
Team-Based Development in Microsoft Office SharePoint Server 2007
http://msdn.microsoft.com/en-us/library/bb428899.aspx
How do we do SharePoint development, including TFS integration? (MCS Finland Team)
http://blogs.msdn.com/vesku/archive/2009/10/25/how-do-we-do-sharepoint-development-including-tfs-integration.aspx
Hope this helps.