DLL.config files and MSI Deployment Projects

[jwinn]

Before I get started writing this question I would like to politely
discourage people that are going to tell me that there are no such thing as
DLL.config files from replying to this post.

About the application:

I have written a windows service that uses modules (aka plugins) that are
loaded into seperate AppDomains (which I configure when I create them) during
runtime so they can be unloaded and updated dynamically without affecting the
other modules that are loaded and in use by the service. There is also a
FileSystemWatcher monitoring the config files used by each domain so the
domain can be reloaded automatically if the configuration changes. The
Windows service has a config file which I have made a custom configuration
section for that tells the service which dll assemblies to load. When loading
those assemblies in order to keep each module portable and seperate from each
other they each get their own dll.config file.

My problem:

I'm trying to create a setup and deployment project for my DLL which has an
app.config file located in the project. When the project is built, the
<assembly>.dll.config file is built correctly and placed in the target
directory. The problem is the installer isn't grabbing the dll.config file
and including it in the MSI file that is being created. I've tried spending
some time googling this to find any potential work arounds however none have
done the trick thus far.

I have tried changing the build type for the app.config to Content and
including content files in the setup project however the config file when
installed ends up being named app.config.

Any help would be appreciated, and thank you for taking the time to read
this wall of text!

- Jeff

 

[Phil Wilson]

I never use the content type of thing (or primary output/project output)
because it's difficult to know what you're getting. I don't know if this is
convenient for you, but I just browse from the folder view (or drag and
drop) to get the files into the folders. That's also the only thing to do if
your output is going to multiple destinations such as the Application
Folder, Common Files, the GAC etc.

 

[navkmh]

If u are using visual studio 2005 or vs.net or the later version,there
s a provision for adding project files.
This is how it can be done
First the setup project is added along with the project here
On that ,add the primary output to the installer which will done by
adding primay files(which included dlls and exe,usually from the debug
of the bin folder of the project)
Also , if u want to add any file in particular,this can be added by
specifying the file which u want to include in the setup file .

Hope it helps,

--Naveen Kumar K M