framework-dotnet

Validate SubZeroFramework builds and diagnose build failures. Use when choosing the right VS Code task, checking service or client compile scope, debugging Uno/WinUI XAML failures, or deciding when task output is not enough and full Visual Studio build output is needed.

Preserve SubZeroFramework reactive, analyzer, and polling conventions. Use when editing Rx subscriptions, DynamicData projections, custom Roslyn analyzers, WinUI bindable state, telemetry current-state caches, or FrameworkDataProvider polling control.

Implement or debug SubZeroFramework service lifecycle controls. Use when editing Settings or Warnings and Issues button enablement, packaged helper readiness, install/update/uninstall/restart/shutdown/autorun gating, or post-action refresh behavior.

Validate telemetry changes in SubZeroFramework. Use for telemetry regressions, reconnect behavior, stream startup or cancellation, history-window validation, DynamicData identity issues, backpressure, shared stream reuse, and IPC-only telemetry UI work.

Keep SubZeroFramework telemetry and inventory UI stable under live updates. Use when editing dashboard, Device Capabilities, or telemetry pages with LiveCharts, stable card collections, Hardware.Info inventory mapping, retained history ordering, or fan capability-driven UI state.