Azure DevOps构建发布控制台应用遇打包及路径问题求助

问题描述 #

当前解决方案包含多个项目，尝试构建并发布控制台应用Migration.Runner时，VSBuild任务未生成预期的Zip包，后续发布任务提示目标路径不存在。原YAML配置片段：

- task: VSBuild@1
  displayName: "Build MigrationRunner"
  inputs:
    solution: '**/Migration.Runner.csproj'
    msbuildArgs: '/p:DeployOnBuild=true /p:WebPublishMethod=Package /p:PackageAsSingleFile=true /p:SkipInvalidConfigurations=true /p:DesktopBuildPackageLocation="$(build.artifactStagingDirectory)\RUNNER\WebApp.zip"'
    platform: '$(buildPlatform)'
    configuration: '$(buildConfiguration)'

- task: PublishPipelineArtifact@1
  displayName: "Publish artifact 'RUNNER Service'"
  inputs:
    targetPath: '$(build.artifactStagingDirectory)\RUNNER\WebApp.zip'
    artifact: 'RUNNER'
    publishLocation: 'pipeline'

需求是将该控制台应用发布到制品库，后续可在发布流水线中解压运行，或提供其他可行方案。

问题原因 #

WebPublishMethod=Package是针对ASP.NET Web应用的发布参数，控制台应用不适用这套参数，导致MSBuild无法正确生成Zip包。

可行解决方案 #

方案1：使用DotNetCoreCLI任务发布（推荐） #

用DotNetCoreCLI@2的publish命令直接生成可发布的包，更适配.NET控制台应用：

- task: DotNetCoreCLI@2
  displayName: "Publish Migration.Runner"
  inputs:
    command: 'publish'
    projects: '**/Migration.Runner.csproj'
    arguments: '--configuration $(buildConfiguration) --output $(build.artifactStagingDirectory)\RUNNER'
    zipAfterPublish: true # 自动生成Zip包

- task: PublishPipelineArtifact@1
  displayName: "Publish RUNNER artifact"
  inputs:
    targetPath: '$(build.artifactStagingDirectory)\RUNNER'
    artifact: 'RUNNER'
    publishLocation: 'pipeline'

• zipAfterPublish: true会在发布目录下自动生成以项目名命名的Zip包，后续发布流水线可直接获取该包解压运行。
• 如果不需要自动Zip，可去掉该参数，直接发布整个输出目录，后续发布时直接运行目录里的exe文件。

方案2：调整VSBuild的MSBuild参数（针对非.NET Core的控制台应用） #

如果是传统.NET Framework控制台应用，修改MSBuild参数为控制台适用的打包方式：

- task: VSBuild@1
  displayName: "Build and package Migration.Runner"
  inputs:
    solution: '**/Migration.Runner.csproj'
    msbuildArgs: '/p:Configuration=$(buildConfiguration) /p:Platform=$(buildPlatform) /p:OutputPath=$(build.artifactStagingDirectory)\RUNNER /t:Build;Publish'
    platform: '$(buildPlatform)'
    configuration: '$(buildConfiguration)'

- task: ArchiveFiles@2
  displayName: "Zip RUNNER output"
  inputs:
    rootFolderOrFile: '$(build.artifactStagingDirectory)\RUNNER'
    includeRootFolder: false
    archiveType: 'zip'
    archiveFile: '$(build.artifactStagingDirectory)\RUNNER\MigrationRunner.zip'
    replaceExistingArchive: true

- task: PublishPipelineArtifact@1
  displayName: "Publish RUNNER artifact"
  inputs:
    targetPath: '$(build.artifactStagingDirectory)\RUNNER\MigrationRunner.zip'
    artifact: 'RUNNER'
    publishLocation: 'pipeline'

• 用/t:Build;Publish触发构建和发布，指定输出目录到制品暂存区。
• 用ArchiveFiles@2任务手动打包输出目录为Zip包，确保路径存在。

后续发布流水线操作 #

发布时可使用ExtractFiles@1任务解压Zip包到目标路径，然后直接运行控制台应用的exe文件：

- task: ExtractFiles@1
  displayName: "Extract RUNNER package"
  inputs:
    archiveFilePatterns: '$(Pipeline.Workspace)/RUNNER/*.zip'
    destinationFolder: '$(Agent.TempDirectory)/MigrationRunner'
    cleanDestinationFolder: true

- task: CmdLine@2
  displayName: "Run Migration.Runner"
  inputs:
    script: |
      cd $(Agent.TempDirectory)/MigrationRunner
      Migration.Runner.exe # 替换为实际的exe文件名

内容的提问来源于stack exchange，提问作者Roelant M