app.config (for a dll) not getting added to setup project

[MJB]

I have several dlls that have app.config files tied to them. When
adding their primary output to a Setup project everything works fine,
but only the app.config for the .exe gets added to the Setup project
automatically. Is there any way to get the app.configs for the dlls
added to the Setup without manually doing "Add File"? Thanks for the
assistance.

Oh, this is a windows service application and I'm using Visual Studio
2005 Prof / .Net 2.0

 

[Galcho[MCSD.NET]]

AFAIK you cannot have .config files for class libraries
if you need them then they read config values at runtime from
app.exe.config file.

this is why VS 2005 add only app.config for exe's

I hope this helps
Galin Iliev[MCSD.NET]
www.galcho.com

 

[MJB]

Actually that was true for .Net 1.x, but with .Net 2.0 / VS 2005 you can
have app.configs for .DLLs and/or .EXEs - basically an app.config per
project. Just right-click a project and click "properties". When you
see the properties screen select "settings" - this is where you would
create an app.config for any project. It works well too in debug mode.
The problem arises when I try to get all of my app.configs to get
bundled up with my setup. Any help would be appreciated.

Thanks

AFAIK you cannot have .config files for class libraries
if you need them then they read config values at runtime from
app.exe.config file.

this is why VS 2005 add only app.config for exe's

I hope this helps
Galin Iliev[MCSD.NET]
www.galcho.com

I have several dlls that have app.config files tied to them. When
adding their primary output to a Setup project everything works fine,
but only the app.config for the .exe gets added to the Setup project
automatically. Is there any way to get the app.configs for the dlls
added to the Setup without manually doing "Add File"? Thanks for the
assistance.

Oh, this is a windows service application and I'm using Visual Studio
2005 Prof / .Net 2.0

 

[Phil Wilson]

The short answer is to just manually add the files you want, Dlls, config
files, whatever. Drag the files into the appropriate folder. This seems to
be a common general issue, the definition of project output. I've never
quite understood why it's popular because when you use it you won't know
what files are actually being installed until you've run the MSI setup.
--
Phil Wilson
[Microsoft MVP-Windows Installer]
Definitive Guide to Windows Installer
http://apress.com/book/bookDisplay.html?bID=280

Actually that was true for .Net 1.x, but with .Net 2.0 / VS 2005 you can
have app.configs for .DLLs and/or .EXEs - basically an app.config per
project. Just right-click a project and click "properties". When you see
the properties screen select "settings" - this is where you would create
an app.config for any project. It works well too in debug mode. The
problem arises when I try to get all of my app.configs to get bundled up
with my setup. Any help would be appreciated.

Thanks

AFAIK you cannot have .config files for class libraries
if you need them then they read config values at runtime from
app.exe.config file.

this is why VS 2005 add only app.config for exe's

I hope this helps
Galin Iliev[MCSD.NET]
www.galcho.com

I have several dlls that have app.config files tied to them. When
adding their primary output to a Setup project everything works fine,
but only the app.config for the .exe gets added to the Setup project
automatically. Is there any way to get the app.configs for the dlls
added to the Setup without manually doing "Add File"? Thanks for the
assistance.

Oh, this is a windows service application and I'm using Visual Studio
2005 Prof / .Net 2.0

 

[MJB]

Phil,

Thanks for the information - though it's not what I was hoping for
. It makes creating a manageable install package somewhat difficult.
Hopefully someone on the .Net/MSI team is reading this.....

Thanks,
Matt

The short answer is to just manually add the files you want, Dlls, config
files, whatever. Drag the files into the appropriate folder. This seems to
be a common general issue, the definition of project output. I've never
quite understood why it's popular because when you use it you won't know
what files are actually being installed until you've run the MSI setup. news:[email protected]...

Actually that was true for .Net 1.x, but with .Net 2.0 / VS 2005 you can
have app.configs for .DLLs and/or .EXEs - basically an app.config per
project. Just right-click a project and click "properties". When you see
the properties screen select "settings" - this is where you would create
an app.config for any project. It works well too in debug mode. The
problem arises when I try to get all of my app.configs to get bundled up
with my setup. Any help would be appreciated.

Thanks

AFAIK you cannot have .config files for class libraries
if you need them then they read config values at runtime from
app.exe.config file.

this is why VS 2005 add only app.config for exe's

I hope this helps
Galin Iliev[MCSD.NET]
www.galcho.com



MJB wrote:
I have several dlls that have app.config files tied to them. When
adding their primary output to a Setup project everything works fine,
but only the app.config for the .exe gets added to the Setup project
automatically. Is there any way to get the app.configs for the dlls
added to the Setup without manually doing "Add File"? Thanks for the
assistance.

Oh, this is a windows service application and I'm using Visual Studio
2005 Prof / .Net 2.0

 

[Chris Dunaway]

Hopefully someone on the .Net/MSI team is reading this.....

Why don't you post it to the Feedback center so they will be sure to
see it?

http://lab.msdn.microsoft.com/productfeedback