C# - Installer Project does not use the App.Config of the exe

Question

0.00/5 (No votes)

See more:

Hi,

I am trying to create a custom action for a installer project (in VS 2005) which will get executed after the installation is completed. This custom action points to the primary output of a dll that has a App.Config file. I have tested this dll independently (by calling from a console application), i had to add the App.Config of the dll in the console application also to make it work.

When i tried installing the installer; after installation the dll is invoked but its not able to detect the App.Config file and hence throws error that "key is not found".

How can i make the installer project use the App.Config of the dll it is invoking?

Regards,
Priya.

Posted 6-Aug-10 2:03am

shivapriyak

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

E.F. Nijboer · Answer 1 · 2010-08-06T02:51:00

You have to add the app.config manually, it is not added by default. This is because it is specific for the environment and would also mean that the web.config could be overwritten in case someone is just performing an update but wants to keep it's own web.config.

So just add it yourself and that's it.

Good luck!