Azure DevOps Pipeline无法从Net Core 3.1应用程序生成单个文件exe

如何解决Azure DevOps Pipeline无法从Net Core 3.1应用程序生成单个文件exe

我想自动化我的部署。到目前为止，我一直在通过Visual Studio 2019手动发布我的Net Core 3.1解决方案，没有任何问题。但是，当我想使用Azure DevOps Pipeline时，即使我没有收到任何错误，我总是以数百个.dll文件而不是一个.exe文件结束。

这是我按预期工作的Visual Studio配置：

<?xml version="1.0" encoding="utf-8"?>
<!--
https://go.microsoft.com/fwlink/?LinkID=208121. 
-->
<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <PropertyGroup>
    <DeleteExistingFiles>True</DeleteExistingFiles>
    <ExcludeApp_Data>False</ExcludeApp_Data>
    <LaunchSiteAfterPublish>True</LaunchSiteAfterPublish>
    <LastUsedBuildConfiguration>Release</LastUsedBuildConfiguration>
    <LastUsedPlatform>Any CPU</LastUsedPlatform>
    <PublishProvider>FileSystem</PublishProvider>
    <PublishUrl>C:\Users\Karel Křesťan\Desktop\apm-local</PublishUrl>
    <WebPublishMethod>FileSystem</WebPublishMethod>
    <SiteUrlToLaunchAfterPublish />
    <TargetFramework>netcoreapp3.1</TargetFramework>
    <RuntimeIdentifier>win-x64</RuntimeIdentifier>
    <PublishSingleFile>True</PublishSingleFile>
    <ProjectGuid>870788a8-f14a-4683-8395-6048e2c9aa1e</ProjectGuid>
    <SelfContained>true</SelfContained>
  </PropertyGroup>
</Project>

如您所见，它是单个文件且包含。

这是我在DevOps上的Yaml文件：

    trigger:
- master

pool:
  vmImage: 'windows-latest'

variables:
  solution: '**/*.sln'
  buildPlatform: 'Any CPU'
  buildConfiguration: 'Release'
  imageName: 'fine-project-manager'

steps:
- task: UseDotNet@2
  inputs:
    packageType: 'sdk'
    version: '3.1.107'

- task: MSBuild@1
  inputs:
    solution: '**/*.sln'
    msbuildArguments: '/t:restore;rebuild;publish /p:DeployOnBuild=True /p:DeployDefaultTarget=WebPublish /p:WebPublishMethod=FileSystem /p:SelfContained=true /p:Platform="Any CPU" /p:Configuration=Release /p:RuntimeIdentifier=win-x64'
    msbuildVersion: latest

- task: MSBuild@1
  inputs:
    solution: '**/*.sln'
    msbuildArguments: '/T:"ApmBackend" /t:publish /p:DeployOnBuild=True /p:DeployDefaultTarget=WebPublish /p:WebPublishMethod=FileSystem /p:SelfContained=true /p:Platform="Any CPU" /p:Configuration=Release /p:PackageAsSingleFile=true /p:RuntimeIdentifier=win-x64 /p:OutputPath=$(Build.ArtifactStagingDirectory)'
    msbuildVersion: latest

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

管道成功运行并发布了应用程序，但是，它不是单个文件。知道什么会引起麻烦吗？

关于管道的小注释： 我正在使用两个MSBuild，因为无法从具有多个项目的解决方案中发布单个文件应用程序的问题找到更好的解决方法。

当我尝试发布解决方案时，每个.csproj文件出现以下错误：

error NETSDK1099: Publishing to a single-file is only supported for executable applications.

这就是为什么我先发布整个解决方案，然后才发布可执行的ApmBackend.csproj的原因。不太干净，但是可以用，我不知道其他修复方法。

解决方法

对于将来尝试在天蓝色下生成单个exe的任何人来说，这是真正有效的yaml（我肯定有一个更简洁，更直接的解决方案，但我找不到它）：

# ASP.NET Core (.NET Framework)
# Build and test ASP.NET Core projects targeting the full .NET Framework.
# Add steps that publish symbols,save build artifacts,and more:
# https://docs.microsoft.com/azure/devops/pipelines/languages/dotnet-core

trigger:
- master

pool:
  vmImage: 'windows-latest'

variables:
  solution: '**/*.sln'
  buildPlatform: 'Any CPU'
  buildConfiguration: 'Release'
  imageName: 'fine-project-manager'

steps:
- task: UseDotNet@2
  inputs:
    packageType: 'sdk'
    version: '3.1.107'

- task: MSBuild@1
  inputs:
    solution: '**/*.sln'
    msbuildArguments: '/t:restore;rebuild;publish /p:DeployOnBuild=True /p:DeployDefaultTarget=WebPublish /p:WebPublishMethod=FileSystem /p:SelfContained=true /p:Platform="Any CPU" /p:Configuration=Release /p:RuntimeIdentifier=win-x64'
    msbuildVersion: latest

- task: DotNetCoreCLI@2
  inputs:
    command: 'publish'
    arguments: -c Release --runtime win-x64 /p:PublishSingleFile=true --self-contained --output $(Build.ArtifactStagingDirectory) --no-dependencies
    projects: $(Build.SourcesDirectory)\ApmBackend\ApmBackend.csproj
    zipAfterPublish: false

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

您当然必须用自己的可执行项目替换ApmBackend.csproj