Best practices to store environment or user options -- dotnet windows forms designtime

Earl
11/21/2007 8:27:06 PM

..Net Winforms app. I'm currently using the database to store user options.
But I wonder if there is a better, faster technique. For a simple example,
look at the Visual Studio 2005 Tools > Options screens ... are all of these
choices being saved XML, a database or where? Is the OK button a "Save"
button or are the changes committed at the time you check/uncheck? I'm doing
everything Winforms and while my system works well, I'm always looking for
fewer trips across the network (so long as it doesn't come at a price!).

jay parzych
11/22/2007 9:49:25 AM

i use the Isolated Storage Settings Helper found here:

http://idesign.net/idesign/DesktopDefault.aspx?tabindex=5&tabid=11

Smart client applications often need to store application settings in a
partial trust environment. For strongly typed settings building
applications with Visual Studio 2005, user settings can be written in
partial trust once .NET 2.0 releases. In addition, sometimes you may
need to store ad-hoc settings in separate files and you may not want to
use user settings for those settings. Isolated storage provides a good
place to put custom settings that can be written to in partial trust.
This helper class allows you to read and write custom settings

simple to use

[quoted text, click to view]

Earl
11/22/2007 9:57:46 AM

Thanks to both for the ideas.

[quoted text, click to view]

newscorrespondent@charter.net
11/22/2007 2:21:10 PM

The stock anwer is "It depends" on what your requirements are. If the
clients of your application don't always work on the same computer a
database is a good choice. When they always work on the same machine you can

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about dotnet windows forms designtime

dotnet windows forms designtime : Best practices to store environment or user options