Linked by Thom Holwerda on Sun 11th Jan 2009 10:54 UTC, submitted by Hiev

Permalink for comment 343055
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Member since:
2005-07-06
1. An amateur would actually have a clue what App.config is for which is why he wrote this:
2. The vast majority of .Net applications are ported from the .Net world to Mono. Ergo, you are bound by what goes on in the Windows based .Net world no matter how many times you write "It only uses App.config you luzer!"
3. You have to explicitly use App.config, it isn't required and it is intended for static global application settings. I'm not even sure App.config can be edited programmatically either. It's certainly not well advertised.
4. App.config is something that only an administrator will have access to and shouldn't be written by the application directly. The registry is certainly the only way of reliably getting per-user settings or setting on the fly application settings, or bunging something in Application Data - which is Windows specific incidentally. A spectacular number of .Net apps do this, and Mono needs to handle it otherwise porting is a no-go.
You're only embarrassing yourself, because if you think that .Net applications all explicitly use App.config for all of their settings (not what it is designed for incidentally) and there is no reason for registry usage in Mono (which there obviously is because you've even been given a link to someone talking of a GTK registry editor to Mono's already built-in registry) then you have no clue whatsoever. Anyone who gives a single thoroughly inciteful comment consisting only of 'Mono rocks' is a few rocks short of a quarry themselves.
Sorry, but porting .Net applications to Mono and other platforms is not as simple as you would so dearly love to make out.
Edited 2009-01-11 19:10 UTC