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.
I have some business objects which use:
Web.Configuration.WebConfigurationManager.AppSettings.Item('SomeSetting') Now that I’m breaking those objects into their own library, it feels dirty to take a dependency on System.Web when nothing else in the library has anything to do with web.
What is the proper way to do this?
UPDATE: Found this example showing per-assembly config files. Is this a bad idea?
Put it in web.config and call ConfigurationManager.AppSettings[‘KEY’]
No need for system.web in your libraries.