Web应用CI/CD流水线配置：缺失「合并所有输出到单个程序集」环节

Got it, let's get this sorted out for you! Since you're collaborating with Microsoft on your CI/CD pipeline (I’m assuming Azure DevOps here given the context), replicating that manual precompile-and-merge setup you used for file system publishing is totally achievable. Here’s a step-by-step breakdown to make it happen:

1. Map Manual Settings to MSBuild Parameters #

The options you checked in the publish profile translate directly to MSBuild properties. We just need to pass these properties in your pipeline's build/publish tasks:

• PrecompileBeforePublish=true: Enables precompilation during publish (matches the "Precompile during publishing" checkbox)
• MergeAllOutputsToSingleAssembly=true: Merges all compiled outputs into one assembly (matches "Merge all outputs to a single assembly")
• SingleAssemblyName=ourProduct: Sets the name of the merged assembly (MSBuild will automatically add the .dll extension)

2. Configure Pipeline Tasks #

Choose the approach that matches your project type:

For .NET Framework Projects (Using MSBuild Task) #

If your pipeline uses the MSBuild task for building/publishing, update the MSBuild arguments field with these parameters:

/p:PrecompileBeforePublish=true /p:MergeAllOutputsToSingleAssembly=true /p:SingleAssemblyName=ourProduct

Make sure your MSBuild target is set to Publish (or a combined target like Build;Publish) to trigger the full publish flow.

For ASP.NET Core Projects (Using DotNetCoreCLI Task) #

For ASP.NET Core, add the same MSBuild properties to the dotnet publish command in your DotNetCoreCLI task's Arguments field:

publish --configuration Release --output $(Build.ArtifactStagingDirectory) /p:PrecompileBeforePublish=true /p:MergeAllOutputsToSingleAssembly=true /p:SingleAssemblyName=ourProduct

Bonus: Bind Settings to Your Publish Profile (.pubxml) #

If you want to keep this configuration tied to your codebase (instead of pipeline tasks), add the properties directly to your existing publish profile file (under Properties/PublishProfiles):

<PropertyGroup>
  <PrecompileBeforePublish>True</PrecompileBeforePublish>
  <MergeAllOutputsToSingleAssembly>True</MergeAllOutputsToSingleAssembly>
  <SingleAssemblyName>ourProduct</SingleAssemblyName>
</PropertyGroup>

Then, in your pipeline task, just reference this publish profile (e.g., /p:PublishProfile=YourProfileName.pubxml) and all settings will be applied automatically.

3. Validate the Output #

After running your pipeline, check the Bin folder in your published artifacts. You should see ourProduct.dll as the main assembly, with all previously scattered outputs merged into it. If you run into issues, check the task logs to confirm the MSBuild parameters were passed correctly, or troubleshoot any precompilation errors that appear.

内容的提问来源于stack exchange，提问作者John Waller