Replace files in the Release folder

[Christoph Schneegans]

Hello!

The help file reads as follows:

Please note that the uncompressed layout, while storing your application files in a readily accessible state, does not permit you to randomly replace those files. Because of the nature of Windows Installer and the way it handles resiliency, if you wish to update any of the files in the installation package, you will have to rebuild the installation. Simply copying the updated file to the proper location in the build folders may cause your installation to fail.

Does this warning really apply? I tried to make my installation fail several times, i.e. I replaced a very small text file in the "Release" folder with a very large one of the same name, and vice versa. The installation never failed, and the proper file was installed. Is it possible to identify the conditions that can make an installation fail when randomly replacing files?

[jimo]

I don't understand this one, I know for a fact that everytime you start the compile IA recursively deletes everything in the release folder for the build type.

If you mean that you are replace a file after you compile the setup package in the releases folder and then run the package without recompiling, well, I would think that this wouldbe unwise, however I have never tested it and do not think that it is advisable.

I'm sure Michael will comment on this as well.

[MichaelNesmith]

This is quite ill-advised. Especially with the new file hashes option for your project in the Project Options dialog, this could break your setup at runtime. Use at your own risk!