Linked by Thom Holwerda on Sun 11th Jan 2009 10:54 UTC, submitted by Hiev
Thread beginning with comment 343033
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
RE: A development platform should be agnostic in design
by Toad on Sun 11th Jan 2009 16:36
in reply to "A development platform should be agnostic in design"
I mean come on, don't you find it odd that your Mono apps compile to exe and dlls with the need for a Windows like registry on Linux/Mac? Why force MS's concept of an operating environment and application behavior in other OSes?
I am not aware that the .net is depended on the registry, in fact I have heard that .net was a way for microsoft of getting rid of dll/registry hell of COM/ACTIVEX. .net uses largly the GAC (global asembly Cash) for shared components, not the registry. For configuration it uses XML Configuration Files both on framework level as on application level.
The only useage of com/registry is that a few methods in the frameworks API is mapped against com method/win32 method in the windows OS that uses the registry, but that is only an implementation details;
So where is the dependency on the registry?
RE[2]: A development platform should be agnostic in des
by Yuske on Sun 11th Jan 2009 17:40
in reply to "RE: A development platform should be agnostic in design"
RE[2]: A development platform should be agnostic in des
by adkilla on Sun 11th Jan 2009 18:24
in reply to "RE: A development platform should be agnostic in design"
I am not aware that the .net is depended on the registry, in fact I have heard that .net was a way for microsoft of getting rid of dll/registry hell of COM/ACTIVEX. .net uses largly the GAC (global asembly Cash) for shared components, not the registry. For configuration it uses XML Configuration Files both on framework level as on application level.
First and foremost, the GAC is meant to cache NGENed assemblies and system components. It does not have any registry like functionality. So what are you trying to mean here? You may want to re-read your post.
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.
-Ad





Member since:
2005-07-07
While I applaud the efforts of the Mono people, they attempts at bringing Microsoft platform technologies to other platforms seems odd as it tries to bring MS's concepts of an operating environment to other platforms.
I mean come on, don't you find it odd that your Mono apps compile to exe and dlls with the need for a Windows like registry on Linux/Mac? Why force MS's concept of an operating environment and application behavior in other OSes?
Java has done a much better job at keeping their platform agnostic of operating environments without having to force a Solaris-like operating environment into other platforms. My Java apps use plists on Macs and registry under Windows as expected by default, the same can't be said of Mono apps.
-Ad