I have a Dll which is added into another solution now my code for reading the configuration file is in DLL
But my configuration file is in current solution
what should be the proper solution ?
Share
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 a Dll which is added into another solution now my code for reading the configuration file is in DLL
But my configuration file is in current solution
what should be the proper solution ?
DLL’s in .NET cannot have their own configuration – that
your.dll.configfile will not be used and interpreted.The basic premise in .NET configuration is that the host application (your main EXE) should have all its configuration in its
app.exe.configfile. So you need to copy & paste your DLL config into the main app’sapp.configfile and you should be fine.See this other SO question with a great, lengthy explanation by Chris Ammerman of why having a DLL config isn’t as trivial as it may seem at first….