问题描述
我们使用的Team Foundation Server和有众多的ASP.NET Web应用程序项目。每个Web应用程序的使用，我们在内部已经开发了一个自定义的内容管理系统。 CMS是本身，一个ASP.NET Web应用程序。
We use Team Foundation Server and have numerous ASP.NET Web Application Projects. Each of the Web Apps uses a custom content management system that we've developed in house. The CMS is itself, an ASP.NET web app.
在部署时，CMS在一个子目录，如/管理员。 CMS是由的.aspx和ASCX文件，以及相应的组件，当然，放置在箱子。
When deployed, the CMS resides in a subdirectory, such as "/Admin". The CMS is comprised of .aspx and ascx files, and the corresponding assemblies are, of course, placed in the bin.
presently，分别存在于每个Web应用程序的源代码控制的CMS文件。换句话说，一个管理文件夹中存在依赖CMS上每个Web应用程序。这带来明显的挑战，因为更新到CMS必须分发到每一个相关的网站。这是我的工作实现自动化/简化这个过程。
Presently, the CMS files exist separately for each Web App in source control. In other words, an "Admin" folder exists in each web application that depends on the CMS. This poses obvious challenges since updates to the CMS must be distributed to every dependent site. It's my job to automate/simplify the process.
我们目前没有进行任何自动构建。我已经在有限的分支TFS源代码管理的知识，我不知道它是适用于这种情况。什么是确保相关项目收到最新的组件和标记从CMS项目的最佳方法是什么？先谢谢了。
We currently do not perform any automated builds. I have limited knowledge of source control branching in TFS and I'm not sure that it's applicable in this scenario. What is the best way to ensure that dependent projects receive the latest assemblies and markup from the CMS project? Thanks in advance.
这听起来像＃2（从'竹）是解决我之后。鉴于共享code已经存在于每个单独的项目，您能简要介绍一下，我会去通过对科/共享CMS的过程？此外，值得注意的是，我不希望传播到相关的项目，只是标记和程序集的.cs文件。这是否改变策略？我应该首先建立在共享项目所需的文件复制到释放文件夹中的生成事件，然后分支释放文件夹？
It sounds like #2 (from 'bamboo) is the solution I'm after. Given that the shared code already resides in each individual project, can you briefly describe the process that I'll go through to "Branch/Share" the CMS? Also, it's worth noting that I do not want the .cs files propagated to the dependent projects, just the markup and assemblies. Does this change the strategy? Should I first create a build event on the shared project to copy the requisite files to a "Release" folder, and then branch the Release folder?
推荐答案
的一对夫妇流行的方式来处理这种情况。
The are a couple popular ways to handle this scenario.
-
该地图为共享的东西给每个应用程序工作区TFS项目，然后包括在每个应用程序的解决方案共享项目。如果你希望所有的球队时，他们建立，因为他们将获得最新的共享的东西，以及使用此方法/应用程序立即获取共享的变化。
Map the TFS project for the shared stuff to each applications workspace and then include the shared project in each applications solution. Use this method if you want all teams/apps to get the shared changes immediately when they build since they will get latest of the shared stuff as well.
科/股的共享资料到每个应用程序的源控件树。这是很容易在TFS的事情。这是非常好的，如果每个队/应用想要当他们获得最新的共同的东西来控制。这使团队能够直到他们准备到共享的东西集成到做他们的事。
Branch/Share the shared stuff into each applications source control tree. This is easy to do in TFS. This is really good if each team/app wants to control when they get the latest of the shared stuff. This keeps the teams being able to do their thing until they are ready to integrate the shared stuff.
我一般总是preFER 2＃。但它确实取决于你如何需要/想工作的具体细节。
I generally always prefer #2. But it really depends on the specifics of how you need/want to work.
这篇关于如何在跨项目共享资源版本的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！