Well, it might seem like, but we are talking about 3 or 4 features the
user can select.
The core feature is planned to include 3 components. These 3 components
make up ~4.000 files. If one component has to be updated all files of
this component have to be changed.
Regards
Michel
Am 21.12.201
Remember that a user never selects components directly. They select features.
My guess is that you want 7 or 8 features that will select the components
required on a per-feature basis.
Edwin G. Castro
Software Developer - Staff
Digital Channels
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.f
stand the implications. No
offense intended.
From: "Michael Scheepers"
Sent: Wednesday, December 21, 2011 9:56 AM
To: chr...@iswix.com, "General discussion for Windows Installer XML
toolset."
Subject: Re: [WiX-users] files and componen
om: "Adams, David"
Sent: Wednesday, December 21, 2011 9:14 AM
To: "General discussion for Windows Installer XML toolset."
Subject: Re: [WiX-users] files and components
Michael:
I would advise against it. Uniquely to Windows Installers, many of us have
made this mistake
Well, I guess I understand the implications.
That brings up my next question. Is it possible to define a component like
and have all subfolders and files added to the msi package? Or do I have
to specify each file like
Michael:
I would advise against it. Uniquely to Windows Installers, many of us have
made this mistake of including multiple files within components "because they
are dependent" only to suffer the consequences later in update situations or
what-not. Overall in software development, it also put
Depends on what kind of files they are and how you plan on servicing them
(patching, upgrades ) Typically these are content type files such as web
content or help content.
But, yes, there are situations where this is acceptable provided that you
understand the implications.
7 matches
Mail list logo
