Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What is the best practice to store constant values that hardly will ever be changed during application life-cycle?
For example there are constant messages to show on UI (and you know exactly application will never be localized) or category-ids that are hard-coded in the database.
It takes too much time to put everything in config. Is it normal to have static constant classes to keep such constants all together? Or may be you should put such values into project resources?
Thank you in advance!
The classic .NET solution to this is to use resource files. Apart from keeping all your code together, this has the added benefit of readying your application for localization.