Bob Arnson írta:
> Szentpali Janos wrote:
>> Can you suggest some strategy to help one install components that do not
>> come in msi-s or msm-s but that are shared/common components that
>> could/would possibly be installed by non msi setups
>
> If you're not using stable component IDs through MSI,
Szentpali Janos wrote:
> Can you suggest some strategy to help one install components that do not
> come in msi-s or msm-s but that are shared/common components that
> could/would possibly be installed by non msi setups
If you're not using stable component IDs through MSI, the closest you'll
get
Bob Arnson írta:
> Szentpali Janos wrote:
>> Does that mean that the same file, installed by two unrelated setup
>> packages into the same path, with two distinct component and file ids
>> (guids) will still be correctly uninstalled/managed?
>
> No, that's what component rules are about. The compo
Szentpali Janos wrote:
> Does that mean that the same file, installed by two unrelated setup
> packages into the same path, with two distinct component and file ids
> (guids) will still be correctly uninstalled/managed?
No, that's what component rules are about. The component GUID and
resource I
Bob Arnson írta:
> Szentpali Janos wrote:
>> "Merge modules are generally now considered bad practice..." If this
>> is true than what is the point of the whole MSI system? I mean if I
>> have a 3rd party component (x.dll) that 4th party and 5th party are
>> using too, how does the system decide th
Szentpali Janos wrote:
> "Merge modules are generally now considered bad practice..."
> If this is true than what is the point of the whole MSI system? I mean if I
> have a 3rd party component (x.dll) that 4th party and 5th party are using
> too, how does the system decide that the x.dll compone
Ugh, I just send this reply but forgort to include the Subject:
Anyway,
Thanks. I did get everything working with the merge module, and I did find the
standalone MSI alternative to the merge module. I hope that the licensing is
the same with the XTal MSI as with the merge module.
I do use Orca
"Merge modules are generally now considered bad practice..."
If this is true than what is the point of the whole MSI system? I mean if I
have a 3rd party component (x.dll) that 4th party and 5th party are using too,
how does the system decide that the x.dll component installed by the 4th
party'
Merge modules are generally now considered bad practice - they become
impossible to service, because the module does not retain its identity. The
only way to service them is to patch the products which have merged the
module. Crystal Reports had a security patch earlier this year:
http://www.micros
9 matches
Mail list logo
