/bundles/itninjaweb/img/Breadcrumb_cap_w.png
I've got an installation which copies files to the target system.
But if the files on the target system are newer, the files will not be copied.
I need to always copy the files.

I use Wise Package Studio 7.0 SP1 to develop MSI's for Windows XP SP3.
I can solve this by first set the action on "Remove file" and later copy the file.
But there must be a better method to do this.
0 Comments   [ - ] Hide Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity

Answers

0
But there must be a better method to do this. If the files do not contain file version information in their header, then no, there's no better way.
Answered 07/05/2011 by: VBScab
Red Belt

Please log in to comment
0
ORIGINAL: VBScab
If the files do not contain file version information in their header, then no, there's no better way.

Yes, 100 % true.
But, I got confused now. What if we use the 'Copy Files' function in WiseScript, there are 3 options for 'Replace Existing Files'.
1. Always 2. Never 3. Check File (Version and Date/Time). Need to check what happens if we choose 'Always'.
Answered 07/05/2011 by: SandeepPanat
Orange Senior Belt

Please log in to comment
0
Why bother with that antique? LOL

All the functionality you need for deleting, copying, replacing or moving files is available natively in MSI.
Answered 07/05/2011 by: VBScab
Red Belt

Please log in to comment
0
ORIGINAL: VBScab

But there must be a better method to do this. If the files do not contain file version information in their header, then no, there's no better way.


Okay, I always did that trick.
The files are in this case XML files.
Another option is to make a Custom Action and copy the files with a vbs or bat.
Answered 07/05/2011 by: subsense
Purple Belt

Please log in to comment
0
Or, you could make it really complicated by employing someone to re-type them longhand in Swahili into Notepad, FTP them to a new folder and employ someone else to translate them back to English. Easy.

Come on! CAs are for use where there is no native MSI functionality.
Answered 07/05/2011 by: VBScab
Red Belt

Please log in to comment
0
Either Use the RemoveFile table to remove the (existing) file on install or set a (real) dummy Version column field value in the File table for the file (ex. 1.0.0.0).
I would recommend the first suggestion
Answered 07/05/2011 by: AngelD
Red Belt

Please log in to comment
1
companion files can be used to deploy non versioned files based on a known files version.

http://blogs.msdn.com/b/astebner/archive/2005/08/30/458295.aspx
Answered 07/06/2011 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
0
Thanks John,

I just love these pages/posts/blog entries where these 'internal workings' kinds of topics are laid out in an understandable, convenient manner, and covered comprehensively. Another one for the bookmarks collection.

Rgds,

PJ
Answered 07/06/2011 by: pjgeutjens
Red Belt

Please log in to comment