This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Excluding Config files from Package
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
May 29, 2014
09:07 AM
Excluding Config files from Package
Hi, we are moving from using Visual studio set-up projects to Install Sheild as we are moving to visual studio 2012. There does not seem to be a way to exclude certain file (such as the web.config) from the install package, as we do not want it to overwrite the web.config on the destination server.
Is there a way of doing this?
Thanks
TM
Is there a way of doing this?
Thanks
TM
(1) Reply
Dec 19, 2014
03:46 PM
I believe this one has to do with Windows install file replacement rules.
http://msdn.microsoft.com/en-us/library/aa371221%28v=vs.85%29.aspx
"Because unnecessary file copying slows an installation, the Windows Installer determines whether the component's key file is already installed before attempting to install the files of any component. If the installer finds a file with the same name as the component's key file installed in the target location, it compares the version, date, and language of the two key files and uses file versioning rules to determine whether to install the component provided by the package. If the installer determines it needs to replace the component base upon the key file, then it uses the file versioning rules on each installed file to determine whether to replace the file."
http://msdn.microsoft.com/en-us/library/aa371221%28v=vs.85%29.aspx
"Because unnecessary file copying slows an installation, the Windows Installer determines whether the component's key file is already installed before attempting to install the files of any component. If the installer finds a file with the same name as the component's key file installed in the target location, it compares the version, date, and language of the two key files and uses file versioning rules to determine whether to install the component provided by the package. If the installer determines it needs to replace the component base upon the key file, then it uses the file versioning rules on each installed file to determine whether to replace the file."