I loose my time in config files
-
I would like to know. Is it only me or your are also spending more time in config files than really writing code with .NET. I really hate this framework because of that. It's not a framework that is made for developer with a good logical mind that like coding. To master this framework you need memory first and be able to manage the config files first. For one day of development on my machine I need 3 days to configure everything on the production server. The code always works fine on my machine. I never get such problem with other languages.
-
I would like to know. Is it only me or your are also spending more time in config files than really writing code with .NET. I really hate this framework because of that. It's not a framework that is made for developer with a good logical mind that like coding. To master this framework you need memory first and be able to manage the config files first. For one day of development on my machine I need 3 days to configure everything on the production server. The code always works fine on my machine. I never get such problem with other languages.
I have no idea what you're spending so much time on or even what config files you're talking about. I usually work on app/web.config files for about 5 minutes ... per project.
A guide to posting questions on CodeProject
Click this: Asking questions is a skill. Seriously, do it.
Dave Kreskowiak -
I would like to know. Is it only me or your are also spending more time in config files than really writing code with .NET. I really hate this framework because of that. It's not a framework that is made for developer with a good logical mind that like coding. To master this framework you need memory first and be able to manage the config files first. For one day of development on my machine I need 3 days to configure everything on the production server. The code always works fine on my machine. I never get such problem with other languages.
Sounds interesting. I had never that problem. I'm working on a web application out for 5 years and made no changes to the config file for ages... It's true that at the beginning I spend about 3 hours to fine tuning everything, but nothing since then... You better get us into the details so we may spot the problem and help you out...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
-
I would like to know. Is it only me or your are also spending more time in config files than really writing code with .NET. I really hate this framework because of that. It's not a framework that is made for developer with a good logical mind that like coding. To master this framework you need memory first and be able to manage the config files first. For one day of development on my machine I need 3 days to configure everything on the production server. The code always works fine on my machine. I never get such problem with other languages.
It really sounds to me like you're doing it wrong. I spend next to no time in config files when I'm developing.
-
I would like to know. Is it only me or your are also spending more time in config files than really writing code with .NET. I really hate this framework because of that. It's not a framework that is made for developer with a good logical mind that like coding. To master this framework you need memory first and be able to manage the config files first. For one day of development on my machine I need 3 days to configure everything on the production server. The code always works fine on my machine. I never get such problem with other languages.
-
I would like to know. Is it only me or your are also spending more time in config files than really writing code with .NET. I really hate this framework because of that. It's not a framework that is made for developer with a good logical mind that like coding. To master this framework you need memory first and be able to manage the config files first. For one day of development on my machine I need 3 days to configure everything on the production server. The code always works fine on my machine. I never get such problem with other languages.
For my web stuff, I spent half a day getting it the way I wanted about four years ago, and then recycle that structure for new projects. Once of the best things I did was to be aware of the different between production and developnent config files, and allow for it: Supporting Development and Release web.config in ASP.NET[^] Nowadays, it takes trivial time to support config files: just a minor tweak to DB connections and I'm off most of teh time. If it's taking your three days, I can't help feeling you are approaching the task wrong...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
I would like to know. Is it only me or your are also spending more time in config files than really writing code with .NET. I really hate this framework because of that. It's not a framework that is made for developer with a good logical mind that like coding. To master this framework you need memory first and be able to manage the config files first. For one day of development on my machine I need 3 days to configure everything on the production server. The code always works fine on my machine. I never get such problem with other languages.
I usually only set database information in the config file, the rest goes in the database. I define it as key/value pairs, but also include "category" and/or machine/module information to be able to filter the necessary. In addition you could add a "user" filter for settings that a user can change. I also add a description on what the key/value pair is for. my two cents. PS: web services/WCF remain a major drag in this...
V.
(MQOTD rules and previous solutions)
