Hi Nate. If you are trying to preserve data while the application is still running then you can use a class or structure to store the data within. Just make sure that the instance object is saved to a variable that has class or global scope. So you might choose to have a variable in your class called UserSettings as type MySettings -- where MySettings is a class with 5 properties, all set from the form's controls. whenever you need to retreive the setting values you just reference UserSettings. If the class goes out of scope (lets say you are talking about your Peripherals form which is used modally) then that variable would be disposed and the valujes lost. So in that case you would store the variable in a more permanent location such as the control that calls the form modally. Then the control can pass the latest version of the settings to the form whenever it is created, saving the last used settings to use for the next time it is opened.
If you are talking about saving data after the process ends so that they are retained for the next time a user opens the application then you have many options available from simple text files to XML to serialized objects. None of these are particularly difficult and can be easily researched through the Help > How Do I... menu item in Visual Studio.
If you are talking about saving data after the process ends so that they are retained for the next time a user opens the application then you have many options available from simple text files to XML to serialized objects. None of these are particularly difficult and can be easily researched through the Help > How Do I... menu item in Visual Studio.