MxmsSettings.json: Difference between revisions
From MXMS Wiki
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
To provide a flexible and scalable environment, we use JSON (JavaScript Object Notation) for all system settings and user preferences which change from instance to instance. | To provide a flexible and scalable environment, we use JSON (JavaScript Object Notation) for all system settings and user preferences which change from instance to instance. | ||
JSON is a lightweight, text-based data format that is easy for humans to read and write, and easy for machines to parse and generate. By modifying the configuration file, you can customize the behavior of the application without needing to touch the underlying source code. | JSON is a lightweight, text-based data format that is easy for humans to read and write, and easy for machines to parse and generate. By modifying the configuration file, you can customize the behavior of the application without needing to touch the underlying source code. | ||
== | == Example configuration == | ||
<pre> | |||
[PersistedState] | |||
public virtual string Name | |||
{ | |||
get; | |||
set; | |||
} | |||
</pre> | |||
Revision as of 06:03, 31 March 2026
To provide a flexible and scalable environment, we use JSON (JavaScript Object Notation) for all system settings and user preferences which change from instance to instance. JSON is a lightweight, text-based data format that is easy for humans to read and write, and easy for machines to parse and generate. By modifying the configuration file, you can customize the behavior of the application without needing to touch the underlying source code.
Example configuration
[PersistedState]
public virtual string Name
{
get;
set;
}
