Note that there are some explanatory texts on larger screens.

plurals
  1. POWPF/C#: Where should I be saving user preferences files?
    text
    copied!<p>What is the recommended location to save user preference files? Is there a recommended method for dealing with user preferences?</p> <p>Currently I use the path returned from <code>typeof(MyLibrary).Assembly.Location</code> as a default location to store files generated or required by the application.</p> <p>EDIT: I found two related/interesting questions:</p> <ul> <li><a href="https://stackoverflow.com/questions/147533/best-place-to-save-user-information-xp-and-vista">Best place to save user information for Windows XP and Vista applications</a></li> <li><a href="https://stackoverflow.com/questions/348022/whats-the-way-to-implement-save-load-functionality">What&#39;s the way to implement Save / Load functionality?</a></li> </ul> <p>EDIT #2: This is just a note for people like me who had never used settings before. Settings are pretty useful, but I had to do a whole bunch of digging to figure out what was going on (coming from the Python world, not something I am used too). Things got complicated as I wanted to save dictionaries and apparently they can't be serialized. Settings also seem to get stored in 3 different files depending on what you do. There is an <code>app.config</code>, <code>user.config</code> and a <code>settings.setting</code> file. So here are two more links that I found useful:</p> <ul> <li><a href="http://social.msdn.microsoft.com/Forums/en-US/csharpgeneral/thread/ddeaca86-a093-4997-82c9-01bc0c630138" rel="nofollow noreferrer">http://social.msdn.microsoft.com/Forums/en-US/csharpgeneral/thread/ddeaca86-a093-4997-82c9-01bc0c630138</a> </li> <li><a href="http://social.msdn.microsoft.com/Forums/en-US/winforms/thread/efe370dc-f933-4e55-adf7-3cd8063949b0/" rel="nofollow noreferrer">http://social.msdn.microsoft.com/Forums/en-US/winforms/thread/efe370dc-f933-4e55-adf7-3cd8063949b0/</a></li> </ul>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload