app.config
-
Explain to me what actually is wrong with ini files that app.config improves upon. Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project!
-
Explain to me what actually is wrong with ini files that app.config improves upon. Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project!
The use of a standardized parser maybe?
Wrong is evil and must be defeated. - Jeff Ello (√-shit)2
-
Explain to me what actually is wrong with ini files that app.config improves upon. Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project!
-
what is wrong? nothing! but what is right? being forced to use kernel calls and the limitations of them, let alone some of those functions no longer work properly is even more of a pain. I am not talking about old code, I am referring to brand new projects the ability to have tightly typed data as an input parameter, allowing customizations to be saved by user is huge. all this by adding a setting. yes you could do the same thing by having layers of ini files, but why? the ability is there with settings and its all managed for us and its easy to work with. Ever try binding an ini to a property grid with 4 lines of code? you can with app.config
-
what is wrong? nothing! but what is right? being forced to use kernel calls and the limitations of them, let alone some of those functions no longer work properly is even more of a pain. I am not talking about old code, I am referring to brand new projects the ability to have tightly typed data as an input parameter, allowing customizations to be saved by user is huge. all this by adding a setting. yes you could do the same thing by having layers of ini files, but why? the ability is there with settings and its all managed for us and its easy to work with. Ever try binding an ini to a property grid with 4 lines of code? you can with app.config
chodi wrote:
being forced to use kernel calls and the limitations of them
There are no kernel calls (beyond file I/O) in either system. And the use of app.config versus .ini is purely a choice of the application developers. Neither system is better than the other.
-
chodi wrote:
being forced to use kernel calls and the limitations of them
There are no kernel calls (beyond file I/O) in either system. And the use of app.config versus .ini is purely a choice of the application developers. Neither system is better than the other.
Those are the ones I am referring to. Currently some do not work, and others require the first line to be blank. I was under the impression they are or were to be depreciated by MS with Windows 8 and removed entirely in 10, can anyone confirm? And for the record, I do not use them unless I am caught, my borrowed and updated routine is much better
-
what is wrong? nothing! but what is right? being forced to use kernel calls and the limitations of them, let alone some of those functions no longer work properly is even more of a pain. I am not talking about old code, I am referring to brand new projects the ability to have tightly typed data as an input parameter, allowing customizations to be saved by user is huge. all this by adding a setting. yes you could do the same thing by having layers of ini files, but why? the ability is there with settings and its all managed for us and its easy to work with. Ever try binding an ini to a property grid with 4 lines of code? you can with app.config
chodi wrote:
the ability to have tightly typed data as an input parameter
First most of it isn't "tightly typed" at least not the way I define it. If you are just reading values out of the app.config and doing zero business validation of them then I suspect you are going to wake up to a surprise someday. Second have you ever created a ill-formed app.config? What happens to your application when you do that? Might note that although it is possible to make a ill-formed ini it is much, much more difficult to do.
chodi wrote:
and its easy to work with
You ever work with a custom part of a app.config? "Easy" is not the term I would use to apply to it.
chodi wrote:
. Ever try binding an ini to a property grid with 4 lines of code? you can with app.config
I don't put user configurations in app.config files or ini files for that matter. So obviously your case would never be relevant to me.
-
Those are the ones I am referring to. Currently some do not work, and others require the first line to be blank. I was under the impression they are or were to be depreciated by MS with Windows 8 and removed entirely in 10, can anyone confirm? And for the record, I do not use them unless I am caught, my borrowed and updated routine is much better
chodi wrote:
Those are the ones I am referring to. Currently some do not work
There is of course a very large difference between saying one type is better than the other versus whether the built in api no longer works. However creating a ini file reader should be an exercise in triviality for an experienced developer. I can do it all of the languages I know with the possible exception of SQL (where it could be done but I just don't know how off hand). And as a matter fact I am rather certain have in fact created my own ini APIs in the past.
-
chodi wrote:
the ability to have tightly typed data as an input parameter
First most of it isn't "tightly typed" at least not the way I define it. If you are just reading values out of the app.config and doing zero business validation of them then I suspect you are going to wake up to a surprise someday. Second have you ever created a ill-formed app.config? What happens to your application when you do that? Might note that although it is possible to make a ill-formed ini it is much, much more difficult to do.
chodi wrote:
and its easy to work with
You ever work with a custom part of a app.config? "Easy" is not the term I would use to apply to it.
chodi wrote:
. Ever try binding an ini to a property grid with 4 lines of code? you can with app.config
I don't put user configurations in app.config files or ini files for that matter. So obviously your case would never be relevant to me.
If you are just reading values out of the app.config and doing zero business validation of them then I suspect you are going to wake up to a surprise someday. never, validation is needed for everything. but isn't it nice to know your data is an integer when you define it as such and don't need to convert from a string? Second have you ever created a ill-formed app.config? What happens to your application when you do that? many many times, more so in 2010. obviously the app will not work, or work properly. backups are a wonderful thing when you remember to use them You ever work with a custom part of a app.config? "Easy" is not the term I would use to apply to it. Actually that is how I started with them, honestly not all that bad, a pain yes. maybe I should also add my question is not fully explained, the powers that be, want to store all data in ini files related to any customization or settings by control, by form, by app, by user, by group instead of one app.config
-
If you are just reading values out of the app.config and doing zero business validation of them then I suspect you are going to wake up to a surprise someday. never, validation is needed for everything. but isn't it nice to know your data is an integer when you define it as such and don't need to convert from a string? Second have you ever created a ill-formed app.config? What happens to your application when you do that? many many times, more so in 2010. obviously the app will not work, or work properly. backups are a wonderful thing when you remember to use them You ever work with a custom part of a app.config? "Easy" is not the term I would use to apply to it. Actually that is how I started with them, honestly not all that bad, a pain yes. maybe I should also add my question is not fully explained, the powers that be, want to store all data in ini files related to any customization or settings by control, by form, by app, by user, by group instead of one app.config
chodi wrote:
maybe I should also add my question is not fully explained, the powers that be, want to store all data in ini files related to any customization or settings by control, by form, by app, by user, by group instead of one app.config
Not sure what sort of app(s) you are working on but I absolutely would not want to store user customizations in the app.config.