Azure归档生成多层嵌套结构：需将Zip根目录设为内容根目录

Alright, let's break down the details that will help us fix that annoying nested folder problem in your zip archive:

• Archive Task Exact Settings

  • The value you’ve entered for the Root folder or file to archive field—this is the most critical piece. Are you targeting the specific subfolder in your build artifact that contains your actual web content (not a parent folder that includes extra layers)?
  • The full path and filename set in Archive file to create (e.g., are you using variables like $(Build.ArtifactStagingDirectory) here, and how is that path structured?)
  • Whether you’ve checked the Prepend root folder name to archive path checkbox—this setting directly controls if the root folder name gets added as a top-level folder in the zip.

• Build Artifact Folder Structure

  • Describe the folder hierarchy of your published build artifact. For example: Does it look like $(Build.ArtifactStagingDirectory)/MyWebProject/bin/Release/PublishOutput with your web files inside the PublishOutput folder?
  • What was the Path to publish value in your Build pipeline’s Publish Build Artifacts task? This determines what gets packaged into the artifact in the first place.

• ASP.NET Web Forms Publish Configuration

  • When you set up the publish step in your Build pipeline (like using MSBuild with a publish profile), what does the publish output structure look like? Does the publish process itself create nested folders that are being carried into the archive?
  • Are you using a custom publish profile? If so, does it define any specific output directory structure that might be adding extra layers?

• Pipeline Code (If Using YAML)

  • If you’re using YAML pipelines instead of the classic visual editor, sharing relevant snippets from your Build and Release pipelines (especially the Archive task and publish-related steps) would let us spot misconfigurations instantly.

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