Files
ILSpy/TestTools/Directory.Packages.props
Siegfried Pammer 1da62d9e08 Add TestTools with the nugetfuzz and decompdiff corpus tools
Both tools have found real decompiler defects (several merged fixes came out of
nugetfuzz sweeps), but they only existed in a private checkout, so nobody else
could run them and their setup knowledge lived in one head. They complement the
fixture suite from the other side: it decompiles code we wrote, these decompile
what the world ships.

They stay outside the solution - file-based apps, run by hand, never by CI - and
the near-empty Directory.Build.props/Directory.Packages.props keep the repo-wide
warnings-as-errors, lock-file and central-package-management settings from
reaching them.

The catalog sweep driver is PowerShell rather than bash so it runs on Windows as
well, which also drops its curl/jq dependency; staging falls back to copying when
Windows withholds symlink privileges, and report file names are hash-truncated to
stay inside the 260-character path limit.

Assisted-by: Claude:claude-opus-5[1m]:Claude Code
2026-08-16 12:15:09 +02:00

8 lines
333 B
XML

<Project>
<PropertyGroup>
<!-- The tools declare their package versions inline with #:package directives, which central
package management forbids. Opting out here keeps the repo's central versions untouched. -->
<ManagePackageVersionsCentrally>false</ManagePackageVersionsCentrally>
</PropertyGroup>
</Project>