The built-in app.config features work fine cross-platform. Even custom
configuration sections and all of that. Our system uses them
extensively for system composition (ie: defining which components should
be started at runtime) on both .NET and Mono. But that type of setting
setup is per-application; it doesn't make an ideal per-user
configuration system unless you create your own construct within it.
Totally feasible, but probably not what the OP was getting at.
On 12/28/2012 08:11 PM, Daniel Lo Nigro wrote:
What's wrong with the built-in Application Settings features in the .NET
Framework? I've never tested this with Mono, but it's been there since
.NET Framework 2.0 so I assume it would work fine. The .NET Framework
handles loading and saving the settings into an XML file, and gives
strongly-typed access to all the properties.
See http://msdn.microsoft.com/en-us/library/k4s6c3a0(v=vs.100).aspx
On Sat, Dec 29, 2012 at 2:49 AM, Hristo Pavlov <hristo_dpav...@yahoo.com
<mailto:hristo_dpav...@yahoo.com>> wrote:
Hello,
What is the recommended way to save user settings files from Mono
across different platforms?
For example I have an XML file with settings that I want to store
somewhere. I thought the IsolatedFileStorage would be a good place
but I have permission problems (read and write) on both Mac OSX and
Linux.
Would the solution require setting file access permissions during
deployment or is there a place a user can always save a file?
Where is the best location on Linux/Mac OSX to store such setting files?
Regards,
Hristo Pavlov
_______________________________________________
Mono-list maillist - Mono-list@lists.ximian.com
<mailto:Mono-list@lists.ximian.com>
http://lists.ximian.com/mailman/listinfo/mono-list
_______________________________________________
Mono-list maillist - Mono-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-list
_______________________________________________
Mono-list maillist - Mono-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-list
