I am having a problem with a Visual Studio 2008 setup and deployment project. The easiest way to describe the problem is by way ofa simple example that copies a file into a directory on a client machine. The problem occurs when a version of the file being copied already exists on the client machine.

If the file on the client machine is newer than the file being copied, the copy does not take place and no warning is given! What I want is for the file to be copied irrespective of whether there is an existing file or what ever version that file happens to be.

I would be most grateful for any help in this regard.

infrazee

The standard file replacement rules for Windows Installer are used in VS 2008 setup projects. These require file versions to be incremented for files that are to be updated. Files that haven't been updated don't need a version increment. This is basically the way every update installworks, whether it's built by VS, InstallShield, WiX etc.No warning is given because it's normal. If you install a Windows Service pack it does the same thing - lower versions do not replace higher versions. If you're not using versioned files, I suggest you start.

---

Phil Wilson

Dear Phil,

Thank you for the reply.

I understand what you have said concerning versioning.

The problem I am experiencing arises when you are deploying things like accdb files containing latest information from central office to branches. These files do not support versioning and whenever they are touched they appear to installation programs to be a later version! Is there anything that can be done to overwrite these types of files?

Thanks

infrazee