Issues

A property with a private setter ({ get; private set; }) is saved but loads back as its default, and the next save erases the stored value

ktsu-dev/AppDataStorage#362 · opened

on Nov 2, 2026

1

A settings property holding NaN or ±Infinity makes Save() throw ArgumentException, and a type whose defaults include NaN can never be loaded (LoadOrCreate and every Get() throw)

ktsu-dev/AppDataStorage#361 · opened

on Nov 2, 2026

1

No release since 1.18.2: pack fails package validation (117 × CP0016) after the Polyfill 11.4.5 bump, so LoadOrCreateIn and the #348/#350 fixes aren't on NuGet

ktsu-dev/AppDataStorage#358 · opened

on Oct 31, 2026

1

Changes queued with QueueSave() are lost when the app is stopped with Ctrl+C, SIGTERM or SIGHUP (docker stop, systemd stop, logout): ProcessExit never fires

ktsu-dev/AppDataStorage#357 · opened

on Oct 29, 2026

1

Two processes saving the same settings file make Save() throw FileNotFoundException/IOException and leave hundreds of archived .bk files

ktsu-dev/AppDataStorage#354 · opened

on Oct 19, 2026

1

A settings file that loaded before an app update makes every Get() throw InvalidOperationException instead of being archived as .corrupt

ktsu-dev/AppDataStorage#353 · opened

on Oct 19, 2026

1

One AppData type failing to save at process exit crashes the process and drops queued saves for every type registered after it

ktsu-dev/AppDataStorage#352 · opened

on Oct 18, 2026

1

Get-only collection properties (`List<string> Items { get; } = []`) are saved but load back empty, and the next save erases them

ktsu-dev/AppDataStorage#341 · opened

on Oct 7, 2026

1

Two AppData<T> types with the same class name (or two closed generics of one class) share one JSON file, and one type's Save silently wipes the other's data

ktsu-dev/AppDataStorage#336 · opened

on Oct 5, 2026

1

Static MySettings.QueueSave()/SaveIfRequired() save the Get() singleton, not the LoadOrCreate() instance, so edits made through LoadOrCreate() are lost or overwritten with stale data

ktsu-dev/AppDataStorage#330 · opened

on Sep 29, 2026

1

Calling QueueSave() on every change means SaveIfRequired() never saves: with no maximum wait, a crash loses everything since the last 3 s idle gap

ktsu-dev/AppDataStorage#329 · opened

on Sep 29, 2026

1

A power loss or OS crash just after a save can leave a zero-length settings file, which LoadOrCreate then silently overwrites with defaults

ktsu-dev/AppDataStorage#325 · opened

on Sep 29, 2026

1

Navigation Menu

Repository navigation

Issues

A property with a private setter ({ get; private set; }) is saved but loads back as its default, and the next save erases the stored value

A settings property holding NaN or ±Infinity makes Save() throw ArgumentException, and a type whose defaults include NaN can never be loaded (LoadOrCreate and every Get() throw)

No release since 1.18.2: pack fails package validation (117 × CP0016) after the Polyfill 11.4.5 bump, so LoadOrCreateIn and the #348/#350 fixes aren't on NuGet

Changes queued with QueueSave() are lost when the app is stopped with Ctrl+C, SIGTERM or SIGHUP (docker stop, systemd stop, logout): ProcessExit never fires

Two processes saving the same settings file make Save() throw FileNotFoundException/IOException and leave hundreds of archived .bk files

A settings file that loaded before an app update makes every Get() throw InvalidOperationException instead of being archived as .corrupt

One AppData type failing to save at process exit crashes the process and drops queued saves for every type registered after it

Get-only collection properties (`List<string> Items { get; } = []`) are saved but load back empty, and the next save erases them

Two AppData<T> types with the same class name (or two closed generics of one class) share one JSON file, and one type's Save silently wipes the other's data

Static MySettings.QueueSave()/SaveIfRequired() save the Get() singleton, not the LoadOrCreate() instance, so edits made through LoadOrCreate() are lost or overwritten with stale data

Calling QueueSave() on every change means SaveIfRequired() never saves: with no maximum wait, a crash loses everything since the last 3 s idle gap

A power loss or OS crash just after a save can leave a zero-length settings file, which LoadOrCreate then silently overwrites with defaults