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 343062
To view parent comment, click here.
To read all comments associated with this story, please click here.
adkilla
Member since:
2005-07-07

If you are really a pro like you fictitiously claim to be then you would provide some links that back your claim. You have yet to explain why you brought up the GAC which has little to nothing to do with the registry.

FYI the configuration files accessible by System.Configuration have the following drawbacks:
"You use one of the Save methods to write configuration information. Note that the user or process that writes must have the following permissions:

* Write permission on the configuration file and directory at the current configuration hierarchy level.
*Read permissions on all the configuration files."

You can refer to this in this MSDN link:
http://msdn.microsoft.com/en-us/library/system.configuration.config...

We've had this experience before when attempting to modify the configuration file. But because the user had no permission to write to "Program Files" directory this was not recommended. You cannot assume the user will always be administrator when using your app!

Instead an MVP advised us to use the registry as MS has recommended here:
"This class provides the set of standard root keys found in the registry on machines running Windows. The registry is a storage facility for information about applications, users, and default system settings. For example, applications can use the registry for storing information that needs to be preserved after the application is closed, and access that same information when the application is reloaded. For instance, you can store color preferences, screen locations, or the size of the window. You can control this data for each user by storing the information in a different location in the registry."
Here is the link for that info in the MSDN .Net reference:
http://msdn.microsoft.com/en-us/library/microsoft.win32.registry.as...

If you do not have any legitimate links to back up your so called facts, then you sir are a charlatan.

-Ad

Reply Parent Score: -1

Yuske Member since:
2005-07-28

We've had this experience before when attempting to modify the configuration file. But because the user had no permission to write to "Program Files" directory this was not recommended. You cannot assume the user will always be administrator when using your app!

If a user doens't have priviledge to write to the program files directory then you use a manifest, the manifest will allow to the user to read tge app.config file, you need to do more investigation, or you are a very bad programmer.

"Charlatan" is a spanish word tha mean
something like scammer, I can write some words in spanish too, "Usted seƱor es un troll ignorante".

Reply Parent Score: 2

adkilla Member since:
2005-07-07

Sheesh, I guess you have a lot to learn besides .Net. The word charlatan I've used is an English word:
http://www.merriam-webster.com/dictionary/Charlatan

You are welcome to rebuke my post with actual references to MS documentation to support your claims.

-Ad

Reply Parent Score: 2

Toad Member since:
2005-11-27

I see you couldn't find anything wrong in what I wrote...

If you are really a pro like you fictitiously claim to be then you would provide some links that back your claim. You have yet to explain why you brought up the GAC which has little to nothing to do with the registry.

If you had any knowledge, you should know that COM that preceded .net used registry to enable COM components (.exe,.dll). It stored information about version, interfaces clasid progid and much more in the registry, metadata that in .net is stored either in .net assembly or GAC, to register .dll in GAC is optional in .net, but is used to share componets, and manage version.
I just showed you that with .net microsoft HAS REMOVED the dependency from the registry. This is basic knowledge.


FYI the configuration files accessible by System.Configuration have the following drawbacks:
[i]"You use one of the Save methods to write configuration information. Note that the user or process that writes must have the following permissions: ....

Of course files must have right permission, this is basic both in Windows as in Linux...

Instead an MVP advised us to use the registry as MS has recommended here...

I would suggest that you shoose better advisors in the future. Registry is the OLD way of storing application data.

If you do not have any legitimate links to back up your so called facts, then you sir are a charlatan.

I see that I hit a nerve somewhere...
I won't spend any of mine time for you, I dislike fanboys that let their libido gets in their way. You are welcome to post any inaccuracy on what I have written.
[/q]

Reply Parent Score: 2

adkilla Member since:
2005-07-07

You are welcome to back up your claims with actual references to MS documentation. Until then what you post here is either inaccurate or fraudulent.

Oh, just because I expose you for the charlatan you are I am a fanboy? Try supporting your claims buddy, your blind MS fanboism doesn't bode well you.

Reply Parent Score: 0

issvb Member since:
2009-01-12

We've had this experience before when attempting to modify the configuration file. But because the user had no permission to write to "Program Files" directory this was not recommended. You cannot assume the user will always be administrator when using your app!

If a non-administrator user should be able to edit the configuration file, maybe you shouldn't store this file in the Program Files directory? Maybe you could use the AppData directory for this ;)

Reply Parent Score: 1