Best Practices for Configuration Management software development (WPF C#)
This case its like a lot of radio buttons, dropdowns (with 10, 20, 600+ options), strings, integers, floats.
A lot means 1000s of each of those.
Configuration s/w means: device A's IP is 000.000.000.000 its FUNCTION is enabled and so on
What are the best approaches for managing this configuration storage and management? Would a relational database (SQL) be more efficient, or would a NoSQL or file-based approach (XML/JSON) be better for handling dynamic settings and historical data?
Additionally, are there any best practices for keeping the UI in sync with fast-changing data in a WPF C# application?
A lot means 1000s of each of those.
Configuration s/w means: device A's IP is 000.000.000.000 its FUNCTION is enabled and so on
What are the best approaches for managing this configuration storage and management? Would a relational database (SQL) be more efficient, or would a NoSQL or file-based approach (XML/JSON) be better for handling dynamic settings and historical data?
Additionally, are there any best practices for keeping the UI in sync with fast-changing data in a WPF C# application?
