[wix-users] Non versioned files

[John Cooper]

The ideal would be a versioned file for the key path, but yes, that should work in practice.

--
John Merryweather Cooper
Senior Software Engineer -- Integration Development Group -- Enterprise Notification Service
Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Office:  913-341-3434x431050
JoCooper at jackhenry.com





-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Neil Hayes
Sent: Monday, August 29, 2016 10:26 PM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] Non versioned files

The e-mail below is from an external source.  Please do not open attachments or click links from an unknown or suspicious origin.

So for each non version file Component I could have a readme.txt as the file key. If a file within that component should change I could update the readme.txt file. That should ensure the payload files are processed?

 


-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of John Cooper
Sent: Monday, August 29, 2016 3:10 PM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] Non versioned files

Pitfall is that the behavior of the Component will be determined by whatever file is the key path.  If it is a non-versioned file, you have non-versioned file behavior (e.g., comparison with the hashes and timestamps, etc.) where in some scenarios the payload files will not be processed.

I would use a key path calculated to have the install/update/repair/uninstall behavior you want for the payload un-versioned files.

--
John Merryweather Cooper
Senior Software Engineer -- Integration Development Group -- Enterprise Notification Service Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Office:  913-341-3434x431050 JoCooper at jackhenry.com




-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Neil Hayes
Sent: Monday, August 29, 2016 7:29 AM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: [wix-users] Non versioned files

The e-mail below is from an external source.  Please do not open attachments or click links from an unknown or suspicious origin.

I think we all agree best practice says 1 file = 1 component and I think this works for you general installs.

I ship over 36,000 files of which 34,000 are not DLL's, exe or OCX's files. Instead they are XML, XSD or other etc.

Would it be safe to group 'n' number of XML files into 1 component, 'n' amount of XSD into another component etc. or should it stay 1 file 1 component?

If grouped what if the max number of files I should put into a component and why?

Pitfalls?

Neil


____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/

NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.


____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/


____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/

NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.