TempFileCollection
gadget
Targets the [Serializable] TempFileCollection in the .NET Framework's in-box System.dll, not the NuGet copy. It deletes target paths on dispose/finalize; -t DELETES them HERE. Below 4.0 strict readers need --legacyfx.
Declared metadata, not a runtime result. How to read evidence.
.\ysonet.exe -g TempFileCollection -hTarget declarations
| Variant | Formatters | Inputs | Requirements | Runtime tokens |
|---|---|---|---|---|
| Default | BinaryFormatter, SoapFormatter, LosFormatter, NetDataContractSerializer, DataContractSerializer | target-path, unc-path | built-in, net-framework | net-fx-2.0, net-fx-3.0, net-fx-3.5, net-fx-4.0, net-fx-4.5, net-fx-4.5.1, net-fx-4.5.2, net-fx-4.6, net-fx-4.6.1, net-fx-4.6.2, net-fx-4.7, net-fx-4.7.1, net-fx-4.7.2, net-fx-4.8, net-fx-4.8.1 |
Options (1)
| Option | Help | Default | Required |
|---|---|---|---|
extrafile= | An ADDITIONAL path to delete on the target. Repeat the option once per extra path (--extrafile "C:\a.txt" --extrafile "C:\b.txt"); -c supplies the first one. A repeatable option is used instead of a separator convention because a Windows path may legitimately contain almost any punctuation. Every path is a path on the TARGET: it is never opened, resolved, canonicalized or checked here, so a relative path resolves against the deserializing process's working directory. Paths that differ only by case are collapsed to one entry, and an empty or whitespace-only value is refused. UNC paths are accepted because File.Delete accepts them. The deletion happens when the target disposes or finalizes the object, which may be immediate, much later, or never if the process exits first, and the framework swallows every failure, so nothing reports back. | Not declared | false |
Credit: [Finders: James Forshaw] [Contributors: Soroush Dalili]