MSI/MSM modules

[Wednesday, March 23, 2005 6:01 PM]

Hi Friedrich,

Any idea when I can include merge modules in my SB5 installs?

Best regards,

Arnór Baldvinsson
Icetips Software
San Antonio, Texas, USA

[Friday, March 25, 2005 11:11 AM]

Arnór,

Sorry for my late reply. We are still investigating if it is possible to
use MSM modules in a non-MSI product (via a MSM import).

Of course, you can already use .msi from within SB5 ("Run Windows Installer"
script item).

A native .msi compiler will be a feature of "SetupBuilder Architect
Edition". Of course, the .msi stuff is not as powerful as the native Win32
installer solution.

I'll keep you posted.

Friedrich

--
Friedrich Linder
CEO, Lindersoft
www.lindersoft.com
1.954.252.3910

[Friday, March 25, 2005 4:53 PM]

Hi Friedrich,

>Sorry for my late reply. We are still investigating if it is possible to
>use MSM modules in a non-MSI product (via a MSM import).
>
>Of course, you can already use .msi from within SB5 ("Run Windows Installer"
>script item).

Unfortunately Crystal Reports only supply their .NET as a MSI, the
rest, i.e. the win32 modules, are in several MSM files.

What tools could be used to suck in the MSM to generate a MSI or
whatever?

Best regards,

Arnór Baldvinsson
Icetips Software
San Antonio, Texas, USA

[Friday, March 25, 2005 5:46 PM]

Arnór,

A merge module (.msm) cannot be installed alone. Merge modules are
simplified .msi files and contain dependent files that act as a functional
group. Merge modules contain additional tables (files, registry settings,
etc.) that are unique to themselves. Something like the SB5 #include
script. To install the information delivered by a merge module with an
application, the module must first be merged into the application's .msi
file. In other words, to use merge modules, you have to support .msi
(InstallShield 10.5, Wise for Windows Installer or ZeroG Windows Installer).

Do you have CR9 or version 10 ?

Friedrich

--
Friedrich Linder
CEO, Lindersoft
www.lindersoft.com
1.954.252.3910

[Friday, March 25, 2005 6:35 PM]

Hi Friedrich,

>file. In other words, to use merge modules, you have to support .msi
>(InstallShield 10.5, Wise for Windows Installer or ZeroG Windows Installer).
>
>Do you have CR9 or version 10 ?

Xi.

Best regards,

Arnór Baldvinsson
Icetips Software
San Antonio, Texas, USA

[Friday, March 25, 2005 5:48 PM]

Arnór,

BTW, please let me know which module(s) you need in .msi format and I can
try to convert it for you.

--
Friedrich Linder
CEO, Lindersoft
www.lindersoft.com
1.954.252.3910

[Friday, March 25, 2005 6:39 PM]

Hi Friedrich,

>BTW, please let me know which module(s) you need in .msi format and I can
>try to convert it for you.

I'm not sure, haven't really had time to look into this yet. This is
what I have:

Crystal11_NET_EmbeddedReporting.msm
CrystalReports11_maps.msm
CrystalReports11_NET_EmbeddedInstall.msi
CrystalReports11_RDC_Designtime.msm
CrystalReports11_RDC_License.msm
CrystalReports11_RDC_Reportengine.msm
CrystalReports11_RDC_Runtime.msm
DotNETCrystalReports.msm

I think I would need:

CrystalReports11_RDC_License.msm
CrystalReports11_RDC_Reportengine.msm
CrystalReports11_RDC_Runtime.msm

Since I'm not distributing the design time stuff I don't think I would
need that.

Right now, for this time around, we are just going to install the std
edition on each machine. It's only 3 machines so it's not deadly<g>

Best regards,

Arnór Baldvinsson
Icetips Software
San Antonio, Texas, USA