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 is
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, the
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 that the
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 IDs
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 component
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 component
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
2007 00:45
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Crystal Reports Merge Module Installation Woes
I am using Wix v3 Build 3.0.3632.0 and am trying to merge the Crystal
Reprots for Visual Studio 2005 merge module into my project. I can not get
the reports to work on the installation
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's
I am using Wix v3 Build 3.0.3632.0 and am trying to merge the Crystal Reprots
for Visual Studio 2005 merge module into my project. I can not get the reports
to work on the installation box. I created identital setups using
InstallShield 9.0 and the Visual Studio 2005 setup projects. BOTH OF
10 matches
Mail list logo
