Set DotnetTool package type when PackAsTool=true

[Copilot]

When PackAsTool=true, nugetizer was not emitting the DotnetTool package type in the nuspec metadata, unlike the built-in .NET SDK Pack.

Changes

• NuGetizer.PackageMetadata.targets: Added condition to set PackageTypes="DotnetTool" when PackAsTool=true and no explicit PackageType is specified
• given_a_tool_project.cs: Added test to verify the package type is set correctly

Result

Projects with PackAsTool=true now correctly emit:

<packageTypes>
  <packageType name="DotnetTool" />
</packageTypes>

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

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

• pkg.kzu.app
  • Triggering command: /usr/bin/dotnet dotnet build (dns block)
  • Triggering command: /usr/bin/dotnet dotnet restore --ignore-failed-sources owner --uid-owner 0 -j ACCEPT (dns block)
  • Triggering command: /usr/bin/dotnet dotnet restore --no-cache (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 the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

When PackAsTool=true in a csproj using nugetizer, the DotnetTool package type is missing.

Expected:

<packageTypes>
  <packageType name="DotnetTool" />
</packageTypes>

in the nuspec/metadata, but it's not there.
if nugetizer is removed and the built-in .NET SDK Pack is used, it properly emits that element.

---

💡 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.

[kzu]

🧪 Details on Microsoft Windows 10.0.26100

from dotnet-retest v1.0.0 on .NET 10.0.1 with 💜 by @devlooped