Fix DotNetCoreCLI@2 zipAfterPublish to preserve ZIP file location

[Copilot]

Issue

When using the DotNetCoreCLI@2 task with zipAfterPublish set to true, the task was removing the produced ZIP file from its original location and placing it inside a newly created directory with the same name as the output path. This resulted in a confusing directory structure where the artifact was an empty folder containing a ZIP file, rather than just the ZIP file itself.

Solution

The fix removes the unnecessary directory creation and file moving logic in the zipAfterPublishIfRequired method:

// Old behavior - created unnecessary directory structure
if (moveZipToOutputSource) {
    fs.mkdirSync(outputSource);
    fs.renameSync(outputTarget, path.join(outputSource, path.basename(outputTarget)));
}

Now when zipAfterPublish is true, the ZIP file remains at the original location where it was created, resulting in a simpler and more intuitive output.

Testing

Created a new test case to ensure the zipAfterPublish functionality works as expected.

Fixes #20974.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• cdn.fwupd.org
  • Triggering command: /usr/bin/fwupdmgr refresh (dns block)
• pkgs.dev.azure.com
  • Triggering command: npm install (dns block)
  • Triggering command: npm install @types/node @types/mocha @types/q @types/ltx @types/uuid @types/semver (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to my firewall allow list

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.