尝试使用“Get”任务时MSBuild生成失败

我正在进行从TFS2010到TFS2012的测试升级。他们正在使用升级模板来运行一组广泛的自定义MSBuild任务,以自动进行构建和部署。MSBuild项目最初是为TFS2005创建的,并在某个时候直接升级到TFS2010。他们正在构建的解决方案主要针对.NET 2.0,并且他们仍在使用VS2005进行大多数开发。

到目前为止,我已经安装了带有Update 1的VS2005、VS2010和TFS2012(按此顺序),并将它们的TFS2010数据库升级到了TFS2012。构建控制器与应用层和数据库位于同一台机器上,因为这是一次“概念验证”升级,以确定在真正升级之前需要在构建过程中解决的任何问题。

当我运行他们的任何基于MSBuild的生成时,我会得到以下错误:

C: \Builds\18\Web\ES集成WebTest\BuildType\TFSBuild.proj(75): 类型的扩展 “Microsoft.TeamFoundation.Build.Client.IBuildDetail”必须为 已配置以便运行此工作流。 C: \Builds\18\Web\ES集成WebTest\BuildType\TFSBuild.proj(75): “获取”任务意外失败。

System.Activities.ValidationException:类型的扩展 “Microsoft.TeamFoundation.Build.Client.IBuildDetail”必须为 已配置以便运行此工作流。

在 System.Activities.Hosting.WorkflowInstanceExtensionCollection。。ctor(活动 工作流定义,工作流实例扩展管理器扩展管理器)

在 System.Activities.Hosting.WorkflowInstanceExtensionManager.CreateInstanceExtensions(活动 工作流定义,工作流实例扩展管理器扩展管理器)

在 System.Activities.Hosting.WorkflowInstance.RegisterExtensionManager(WorkflowInstanceExtensionManager 扩展管理器)

位于System.Activities.WorkflowApplication.EnsureInitialized()

在 System.Activities.WorkflowApplication.RunInstance(工作流应用程序 实例)

在System.Activities.WorkflowApplication.Invoke(活动活动, IDictionary `2个输入,WorkflowInstanceExtensionManager扩展, TimeSpan超时)

在System.Activities.WorkflowInvoker.Invoke(活动工作流, IDictionary `2个输入,TimeSpan超时, 工作流实例扩展管理器扩展)

在 Microsoft.TeamFoundation.Build.Tasks.WorkflowTask.ExecuteInternal()(微软团队基金会内部版本任务工作流任务执行内部)

位于Microsoft.TeamFoundation.Build.Tasks.Task.Execute()

在 Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()

在 Microsoft.Build.BackEnd.TaskBuilder.d__20.MoveNext()

我已经把构建简化为一个非常小的案例,重现了这个问题。完整的.proj文件如下所示:

<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="DesktopBuild" xmlns="http://schemas.microsoft.com/developer/msbuild/2003" ToolsVersion="4.0">

    <!-- Do not edit this -->
    <Import Project="$(MSBuildExtensionsPath)\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets" />
    <ProjectExtensions>
        <!--  DESCRIPTION
     The description is associated with a build type. Edit the value for making changes.
    -->
        <Description>Builds and Deploys the BE site to the integration environment</Description>
        <!--  BUILD MACHINE
     Name of the machine which will be used to build the solutions selected.
    -->
        <BuildMachine>[redacted]</BuildMachine>
    </ProjectExtensions>
    <PropertyGroup>
        <!--  TEAM PROJECT
     The team project which will be built using this build type.
    -->
        <TeamProject>Web</TeamProject>
        <!--  BUILD DIRECTORY
     The directory on the build machine that will be used to build the
     selected solutions. The directory must be a local path on the build
     machine (e.g. c:\build).
    -->
        <BuildDirectoryPath>c:\build</BuildDirectoryPath>
        <!--  DROP LOCATION
      The location to drop (copy) the built binaries and the log files after
     the build is complete. This location has to be a valid UNC path of the
     form \\Server\Share. The build machine service account and application
     tier account need to have read write permission on this share.
    -->
        <DropLocation>\\[redacted]\BuildDrop</DropLocation>
        <!--  TESTING
     Set this flag to enable/disable running tests as a post build step.
    -->
        <RunTest>True</RunTest>
        <!--  WorkItemFieldValues
      Add/edit key value pairs to set values for fields in the work item created
      during the build process. Please make sure the field names are valid 
      for the work item type being used.
    -->
        <WorkItemFieldValues>Symptom=build break;Steps To Reproduce=Start the build using Team Build</WorkItemFieldValues>
        <!--  CODE ANALYSIS
       To change CodeAnalysis behavior edit this value. Valid values for this
       can be Default,Always or Never.

     Default - To perform code analysis as per the individual project settings
     Always  - To always perform code analysis irrespective of project settings
     Never   - To never perform code analysis irrespective of project settings
     -->
        <RunCodeAnalysis>Default</RunCodeAnalysis>
        <!--  UPDATE ASSOCIATED WORK ITEMS
     Set this flag to enable/disable updating associated workitems on a successful build
    -->
        <UpdateAssociatedWorkItems>false</UpdateAssociatedWorkItems>
        <!-- Title for the work item created on build failure -->
        <WorkItemTitle>Build failure in build:</WorkItemTitle>
        <!-- Description for the work item created on build failure -->
        <DescriptionText>This work item was created by Team Build on a build failure.</DescriptionText>
        <!-- Text pointing to log file location on build failure -->
        <BuildlogText>The build log file is at:</BuildlogText>
        <!-- Text pointing to error/warnings file location on build failure -->
        <ErrorWarningLogText>The errors/warnings log file is at:</ErrorWarningLogText>
    </PropertyGroup>



    <PropertyGroup>
        <SourceBranchPath>Main</SourceBranchPath>
    </PropertyGroup>

  <!-- Does some basic validation of the environment before the build starts -->
  <Target Name="PreBuildValidations" >
    <Get FileSpec="$/Web/$(SourceBranchPath)/BuildFiles/Tools/PSExec.exe" Workspace="$(WorkspaceName)" Recursive="false" Force="true" TeamFoundationServerUrl="$(TeamFoundationServerUrl)"/>
  </Target>

    <Target Name="BeforeGet">
        <CallTarget Targets="PreBuildValidations" />
    </Target>


</Project>