TFS2008 到 TFS2010 迁移升级 [英] TFS2008 to TFS2010 migration upgrade

问题描述

全部，

我目前正在尝试创建一个可重复的过程，以将 TFS 2008 安装升级到新硬件，Microsoft 称之为迁移升级，但在新硬件上构建 VS 2008 项目时遇到问题.

I'm currently in the process of attempting to create a repeatable process for the upgrade of a TFS 2008 installation to new hardware in what Microsoft call a migration upgrade, but am experiencing issues when building the VS 2008 projects on the new hardware.

我们的 TFS 2008 安装由两台机器组成；一个用于存放 SQL 数据库和应用层，另一个用作专用的构建服务器.

Our TFS 2008 installation consists of two machines; one which houses the SQL databases and Application Tier, and the other which acts as a dedicated Build Server.

我们安装 TFS 2010 的新硬件由两台机器组成；其中包含 SQL 数据库、应用层、SharePoint 和报告服务.

The new hardware for our TFS 2010 installation consists of two machines; one which houses the SQL databases, Application Tier, SharePoint and the Reporting Services.

到目前为止，我已经成功地将必要的 TFS 数据库从原始服务器重复备份到新服务器并恢复它们，然后使用 'tfsconfig import' 命令成功地将数据库导入并升级到团队项目收藏.团队项目集合正确显示，并且可以立即使用.所有安全设置、搁置集、工作区等都完好无损.

So far, I have managed to successfully repeat the backup of the necessary TFS databases from the original server to the new server and restore them, followed by the 'tfsconfig import' command to successfully import and upgrade the databases to a Team Project Collection. The Team Project Collection appears correctly, and it is immediately usable. All security settings, shelvesets, workspaces etc. are intact.

当我们开始尝试构建解决方案时，我们的问题就开始了.我们最初尝试构建这些解决方案，既不将它们升级到 VS 2010 格式，也不修改任何项目的目标框架.

Our issues start when we begin trying to build solutions. We are initially trying to build these solutions without upgrading them to the VS 2010 format, nor modifying the target Framework of any of the projects.

我们在构建各种项目时遇到以下错误:

We get the following errors when various projects build:

<文件名>.resx(x,y): 错误 RG0000: 找不到名称的类型.类型名称是 'System.Collections.Generic.List`1[[<类>, <汇编>，版本=a.b.c.d，文化=中性，PublicKeyToken=9557797252b44220]]，mscorlib，版本=2.0.0.0，文化=中性，PublicKeyToken=b77a5c561934e089'.线 x，位置 y.[<项目文件名>]

< filename>.resx(x,y): error RG0000: Could not find a type for a name. The type name was 'System.Collections.Generic.List`1[[< class>, < assemnbly>, Version=a.b.c.d, Culture=neutral, PublicKeyToken=9557797252b44220]], mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'. Line x, position y. [< projectfilename>]

ResGen:错误 RG0000:无法加载引用的程序集<文件名>.dll".捕获 FileNotFoundException 说无法加载文件或程序集 '.dll' 或其依赖项之一.系统找不到指定的文件.".[<项目文件名>]

ResGen : error RG0000: Could not load referenced assembly "< filename>.dll". Caught a FileNotFoundException saying "Could not load file or assembly '< filename>.dll' or one of its dependencies. The system cannot find the file specified.". [< projectfilename>]

编译工作流相关项目时出现的各种模棱两可"的 MSBuild 目标引用:

Various 'ambiguous' MSBuild target references when compiling workflow-related projects:

C:\Program Files (x86)\MSBuild\Microsoft\Windows Workflow Foundation\v3.5\Workflow.VisualBasic.Targets (153):GeneratedCodeAttribute"在命名空间System.CodeDom.Compiler"中不明确.

C:\Program Files (x86)\MSBuild\Microsoft\Windows Workflow Foundation\v3.5\Workflow.VisualBasic.Targets (153): 'GeneratedCodeAttribute' is ambiguous in the namespace 'System.CodeDom.Compiler'.

关于如何消除这些问题有各种建议，包括修改 ResGen 上的 32 位支持标志，或强制使用 64 位 ResGen，以及将项目升级到 VS 2010 格式并将其更改为目标框架 4.

There are various suggestions about how to eliminate these issues, including modifying the 32-bit support flag on ResGen, or forcing the use of the 64-bit ResGen, and upgrading projects to VS 2010 format and changing them to target Framework 4.

问题 1.可以通过将有问题的项目更改为目标框架 4 来修复，但是由于兼容性问题，这个特定项目还不能升级，我还没有找到问题 2 的解决方案. &3.

Issue 1. can be fixed by changing the offending projects to target Framework 4, however this particular project cannot be upgraded yet due to compatibility issues, and I have not yet found a solution for issues 2. & 3.

我们有超过 20 个团队项目，每个项目都有多个分支，因此(由于所涉及的工作量很大)希望避免手动更改所有项目/解决方案(特别是因为某些产品还不能升级到框架 4出于兼容性原因，在 Framework 4 MSBuild 中构建针对 Framework 3.5 的项目似乎并不像 Microsoft 让我们相信的那样兼容).

We have upwards of 20 Team Projects, with multiple branches in each, and would therefore (due to the amount of work involved) like to avoid manually changing all projects/solutions (especially as some products cannot be upgraded to Framework 4 yet for compatibility reasons, and building Framework 3.5 targeted projects in Framework 4 MSBuild does not appear to be as compatible as Microsoft would have us believe).

如果任何人有任何的想法可能会被证明有帮助，那么请告诉我.

If anybody has any ideas which may prove helpful, then please let me know.

干杯，

安东尼

问题 1 已被其他人看到，与引用自定义类型的通用列表的资源文件有关.事实证明，这些在我们的项目中是多余的，所以我干脆删除了它们，这个构建问题已经成为历史.

问题 2 似乎完全消失了，可能是因为修复了问题 1.

问题 3 与在 MSBuild 4 中构建 VS2008 工作流项目有关，当它们面向 Framework 3.5 时.微软以其无穷的智慧显然选择不解决这个问题(链接到连接站点)，并且有几个想法可以修复它(参考框架的特定版本，将构建工作流更改为使用 MSBuild 3.5)，但都不起作用.

Issue 3 relates to building VS2008 Workflow projects in MSBuild 4, when they target Framework 3.5. Microsoft, in their infinite wisdom, have apparently chosen to not address this issue (Link to Connect site), and there are several ideas to fix it (referencing specific versions of the Framework, changing the build workflow to use MSBuild 3.5), none of which work.

因此，我们似乎暂停了到 2010 年的升级，直到我们为其构建 3.5 工作流的产品(CRM 4.0 和 SharePoint 2007/2010)支持 Framework 4，或者直到 Microsoft 解决问题.

Microsoft 已承认存在问题，并已发布与上述 KB 编号相关的以下信息: http://support.microsoft.com/kb/2023579

推荐答案

正如我在我的原始帖子中的评论补充中所述，与未构建的工作流相关的这个问题确实通过 Microsot .Net Framework 4 Extended 的补丁解决了，KB2023579 中对此进行了概述，该文件尚未公开(在本文发布时).

As stated in my commented addition on my original post, this issue relating to the workflows not building is indeed resolved by a patch for the Microsot .Net Framework 4 Extended, which is outlined in KB2023579, which has not yet been made public (at the time of this post).

此解决方案由 Microsoft 通过支持电话提供，因此我受该电话的条款和条件的约束，这会阻止我分发补丁链接，直到官方知识库文章可用，点我会发布链接.对不起.

This solution was provided by Microsoft through a support call, and as such I am bound by the terms and conditions of that call, which prevent me from distributing a link to the patch until the official KB article is made available, at which point I will post the link. Sorry.

这篇关于TFS2008 到 TFS2010 迁移升级的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！