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 to develop extension for legacy application that relies on com objects.
My extension is implemented as com-server-in-dll (.net assembly) with MSVS and installed in [program files][company] folder (distributed as msi file).
What is the best practice to configure that: put app.config to installation folder (i suspect there would be some mess to upload that as host process has no app.config at all) or keep old days practice to deal with system registry?
What would you personally prefer?
As your application is hosted by a “legacy” application that uses registry-style configuration, I’d stick with that.
In particular, figuring out where to put an
app.configmight get confusing to you (as a developer) and your users. Worse, this is a different way from what anyone else coming to maintain the application in future would expect.