Linked by Thom Holwerda on Sun 11th Jan 2009 10:54 UTC, submitted by Hiev
Mono Project Arstechnica reports that Mono, an open source implementation of .NET runtime, is bringing Microsoft's development technologies to some unexpected places, including the iPhone, Android, and the Wii.
Thread beginning with comment 343055
To view parent comment, click here.
To read all comments associated with this story, please click here.
segedunum
Member since:
2005-07-06

The .Net and Mono applicatios work with the App.config file(a XML file that store all the applicaitions settings), it doesn't nee the registry at all, even an amateur would know that.

1. An amateur would actually have a clue what App.config is for which is why he wrote this:

"The XML configuration files and MANIFESTs are mostly static and are meant to make it easy for editing by hand and are for setting configuration before the application loads. Application settings generated during runtime by a majority of .Net apps are stored in the registry."


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.

Please, stop posting already, you are embarazing your self.

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

Reply Parent Score: 1

google_ninja Member since:
2006-02-05

You should stop correcting people about things you know nothing about.

The registry is the old school way of doing configuration. App.config is the way that all .net apps are supposed to use. There is an entire namespace devoted to working with these files in System.Configuration. When using the .net configuration APIs, you specify whether you want to do application or user specific changes. If it is user specific, an app.config is generated in that users appdata folder.

You obviously know nothing about .net development, so why in the world would you jump in and correct the OP? I have been doing .net apps for about 3 years now and am very active in the .net open source community, and the only times I every see registry being used is when dealing with a legacy platform (like COM)

Edited 2009-01-11 21:50 UTC

Reply Parent Score: 3

segedunum Member since:
2005-07-06

You should stop correcting people about things you know nothing about. The registry is the old school way of doing configuration. App.config is the way that all .net apps are supposed to use.

I've just explained to you what App.config is for and where it is used. It is not intended to be used for dynamic configuration settings that a great many applications have a need for. Persisting values to App.config when the application is running and using it in that way has never been advised. About all it's good for is connection strings to databases and application wide and user specific settings for configuring the app at startup that aren't going to change much. It's a command line switch replacement really.

For crying out loud. Why on Earth do you think it's called App.config? Because it is strictly for the app configuration. Developers have a wide need to store a great deal of persistable information beyond static application settings. You have to look at other methods such as the registry (well, it's already there) or isolated storage of come kind or roll your own. It gets even more complicated with thread safety.

When using the .net configuration APIs, you specify whether you want to do application or user specific changes.

For quite a while Microsoft hadn't even thought of application settings for particular users! It's really only useful in the development process for testing more than anything else so you don't end up with a proliferation of various settings in source control for different environments. That's why it is a text file after all, as it makes this easier. For other things, it's not the right solution.

You obviously know nothing about .net development, so why in the world would you jump in and correct the OP? I have been doing .net apps for about 3 years now and am very active in the .net open source community..........

ROTFL.

Well, I hope your applications aren't doing anything terribly complex and you obviously missed the memo on how App.config is used and what it is intended for for someone so active in the .Net community, that's all I've got to say.

....and the only times I every see registry being used is when dealing with a legacy platform (like COM)

You need to get out a lot more. Once again, if it was that easy Mono wouldn't have to deal with the registry in ported apps. It quite clearly does.

Reply Parent Score: 2

Manuma Member since:
2005-07-28

WTF? dude, stfu already, what a clueles troll. The app.config file is part of the domain of the application, and since all .NET applications run in a sandbox the .exe and the app.config run in the same domain.

The manifest is just to let know vista that it will need admin. priviledges, but this is in general, even Java apps. would need a manifest for the same porpose, because is a requirement of the OS, and is for all the applications, cross platform or not.

Im really getting tired of your clueless none sense trollish, so please, DON'T TALL ABOUT THINGS YOU DON'T KNOW JUST FOR TROLLING.

Reply Parent Score: 4

segedunum Member since:
2005-07-06

WTF? dude, stfu already, what a clueles troll. The app.config file is part of the domain of the application, and since all .NET applications run in a sandbox the .exe and the app.config run in the same domain. The manifest is just to let know vista that it will need admin. priviledges..............

The issue here is how application developers are dealing with persistable storage of settings, perhaps on a per-user basis, that are amended and used on-the-fly by the application, with all the issues that entails.

Since you clearly didn't understand what App.config is actually for I'm moderately interested in what this meaningless load of claptrap has to do with that?

Reply Parent Score: 2

adkilla Member since:
2005-07-07

Then both of you noobs are welcome to point out to segedunum and me with links from MS documentation, that what you claim is the new way of doing things.

-Ad

Reply Parent Score: 0

google_ninja Member since:
2006-02-05

Look at *anything* in all of system.configuration. There are a few hundred classes, all of which have to do with app.config and user.config, not the registry

http://msdn.microsoft.com/en-us/library/system.configuration.aspx

a google of "configuration .net" would have led you to about 37 million pages all talking about it, again, nothing to do with the registry

http://www.google.ca/search?hl=en&rlz=1C1GGLS_enCA309CA309&sa=X&oi=...

If you don't want to wade through millions of blog posts, here is a pretty good tutorial on codeproject, complete with examples on how to use the configuration api. Again, nothing to do with the registry

http://www.codeproject.com/KB/cs/SystemConfiguration.aspx

Reply Parent Score: 2