Azure DevOps多解决方案多项目依赖YAML流水线构建报错求助

问题背景 #

仓库包含多个基于.NET 4.7.1的解决方案，项目间存在依赖关系：Solution_B.Project_B1依赖Solution_A.Project_A1，Solution_A.Project_A1依赖Solution_A.Project_A2，最终需要构建WPF应用包。原流水线运行时，MSBuild@1任务因找不到Solution_A.Project_A2.dll报错，原流水线配置如下：

trigger:
  - none
#- desarrollo

pool:
  vmImage: 'windows-latest'

variables:
  buildPlatform: 'x64'
  buildConfiguration: 'Release'

steps:
- task: NuGetToolInstaller@1

- task: NuGetCommand@2
  inputs:
    restoreSolution: 'Folder1/Solution_A.sln'

- task: VSBuild@1
  inputs:
    solution: 'Folder1/Solution_A.sln'
    msbuildArgs: '/p:AzureBuild=true /p:DeployOnBuild=true /p:WebPublishMethod=Package /p:PackageAsSingleFile=true /p:SkipInvalidConfigurations=true /p:PackageLocation="$(build.artifactStagingDirectory)"'
    platform: '$(buildPlatform)'
    configuration: '$(buildConfiguration)'

- task: MSBuild@1
  inputs:
   solution: 'Folder2/Solution_B/Project_B1.csproj'
   msbuildArguments: '/p:AzureBuild=true /p:DeployOnBuild=true /p:WebPublishMethod=Package /p:PackageAsSingleFile=true /p:SkipInvalidConfigurations=true /p:PackageLocation="$(Build.ArtifactStagingDirectory)"'
   platform: '$(buildPlatform)'
   configuration: '$(buildConfiguration)'

- task: CopyFiles@2
  displayName: 'Copy Files to: $(Build.ArtifactStagingDirectory)'
  inputs:
    SourceFolder: '$(Build.SourcesDirectory)'
    Contents: '**\bin\release\**'
    flattenFolders: false
    TargetFolder: '$(Build.ArtifactStagingDirectory)'

- task: PublishBuildArtifacts@1
  inputs:
    PathtoPublish: '$(Build.ArtifactStagingDirectory)'
    ArtifactName: 'GicoopPlus'
    publishLocation: 'Container'

错误原因 #

1. 单独构建项目导致依赖无法解析：直接构建Project_B1.csproj时，MSBuild无法自动识别跨解决方案的依赖文件路径，Solution_A的构建产物默认存放在各自项目的bin/x64/Release目录，Project_B1构建时找不到这些依赖DLL。
2. 错误的MSBuild参数：WebPublishMethod是针对Web应用的打包参数，不适用于WPF桌面应用，会导致打包逻辑异常。
3. CopyFiles路径不精确：原路径**\bin\release\**未区分平台（x64），可能收集到其他平台的文件，或遗漏正确路径下的依赖。

修正后的流水线配置 #

trigger:
  - none
#- desarrollo

pool:
  vmImage: 'windows-latest'

variables:
  buildPlatform: 'x64'
  buildConfiguration: 'Release'
  # 统一输出目录，让所有构建产物集中存放，方便依赖引用和后续收集
  outputDir: '$(Build.SourcesDirectory)/BuildOutput'

steps:
- task: NuGetToolInstaller@1

# 还原所有解决方案的NuGet包，确保依赖包都已下载
- task: NuGetCommand@2
  inputs:
    restoreSolution: '**/*.sln'
    feedsToUse: 'select'

# 先构建依赖的Solution_A，MSBuild会自动处理内部项目依赖
- task: VSBuild@1
  inputs:
    solution: 'Folder1/Solution_A.sln'
    msbuildArgs: >
      /p:AzureBuild=true
      /p:SkipInvalidConfigurations=true
      /p:OutDir=$(outputDir)
      /p:Configuration=$(buildConfiguration)
      /p:Platform=$(buildPlatform)
    platform: '$(buildPlatform)'
    configuration: '$(buildConfiguration)'

# 再构建Solution_B，此时Solution_A的产物已在统一输出目录，可被自动引用
- task: VSBuild@1
  inputs:
    solution: 'Folder2/Solution_B/Solution_B.sln'
    msbuildArgs: >
      /p:AzureBuild=true
      /p:SkipInvalidConfigurations=true
      /p:OutDir=$(outputDir)
      /p:Configuration=$(buildConfiguration)
      /p:Platform=$(buildPlatform)
      # 如果需要生成WPF应用包（如ClickOnce），添加以下参数，需提前在VS中创建发布配置文件
      # /p:DeployOnBuild=true
      # /p:PublishProfile=YourPublishProfileName.pubxml
    platform: '$(buildPlatform)'
    configuration: '$(buildConfiguration)'

# 从统一输出目录复制文件到制品目录
- task: CopyFiles@2
  displayName: 'Copy Build Outputs to Artifact Staging Directory'
  inputs:
    SourceFolder: '$(outputDir)'
    Contents: '**/*'
    flattenFolders: false
    TargetFolder: '$(Build.ArtifactStagingDirectory)'

- task: PublishBuildArtifacts@1
  inputs:
    PathtoPublish: '$(Build.ArtifactStagingDirectory)'
    ArtifactName: 'GicoopPlus'
    publishLocation: 'Container'

关键改动说明 #

1. 统一输出目录：通过/p:OutDir=$(outputDir)指定所有项目的构建产物输出到同一个目录，确保跨解决方案的依赖文件能被后续构建任务找到。
2. 构建完整解决方案：不再单独构建单个项目，而是按依赖顺序构建Solution_A.sln和Solution_B.sln，MSBuild会自动处理项目间的依赖关系，确保先构建被依赖的项目。
3. 移除不适用的参数：删除WebPublishMethod等针对Web应用的参数，若需打包WPF应用（如ClickOnce），使用DeployOnBuild配合发布配置文件（需提前在Visual Studio中创建）。
4. 精确CopyFiles路径：直接从统一输出目录复制文件，避免路径匹配错误。

内容的提问来源于stack exchange，提问作者Cisco Cabe