Deploying (MSI) my too also deploys a xxx.exe.config file? [C# 2003 .Net 1.1]
Not sure if this is normal or not but I created a deployment project for my tool (tool.exe) which was created using VSC# 2003 .Net 1.1 and after running the MSI (installing) there is a tool.exe.config file that also appears (I can also see it in primary outputs of the deployment project).
If I delete the file after install the tool.exe still runs fine and I see no reason to keep it (I kind of liked that it was a one-file deployment) so I wanted to know a few things:
- Is there a reason to keep this file post-install?
- Is there a way to remove it from the outputs of my MSI package (deployment package)?
Because I don't recall ever adding it before and I don't see anywhere I can remove it from the outputs of the project...
Any information or help would be much appreciated...
Thanks,
[835 byte] By [
Shaitan00] at [2007-11-20 9:40:19]
# 1 Re: Deploying (MSI) my too also deploys a xxx.exe.config file? [C# 2003 .Net 1.1]
where will your app store the user settings if you delete that file?
Anyway, to remove it:
You made the MSI and when asked what you wanted in it, you chose "primary output of MYPROJECT"
Either:
Add a filter to the MSI so that *.config files are not included
Or, simply tell your MYPROJECT not to output the config file
Your setup will remain one-file deployment only as long as the output from your project is one file. as soon as you use a dll or something that is copied to the out directory (MDB?) then you will have more than one item in the output.. As noted, the clue is in the "Primary output from <project name>" entry of what i in your msi
cjard at 2007-11-9 11:34:28 >
