David Stindl wrote:
> Yes, but you can control dependencies between installed MSM modules,
> so you can force to install one module before another...
>
Once modules are merged in, their components lose their identity as a
set. The resources of all components in the package are installed during
Yes, but you can control dependencies between installed MSM modules,
so you can force to install one module before another...
David.
2007/9/5, Bob Arnson <[EMAIL PROTECTED]>:
> David Stindl wrote:
> > You can e.g. specify, the module has to be installed:
> >
> >
> --
> sig://boB
> http://joyofset
David Stindl wrote:
> You can e.g. specify, the module has to be installed:
>
> http://joyofsetup.com/
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log
You can e.g. specify, the module has to be installed:
can't control how they're installed.
>
> --
> sig://boB
> http://joyofsetup.com/
>
>
>
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files t
David Stindl wrote:
> Maybe the easiest solution should be to use two MSM files in one MSI
> and with dependencies force to install first MSM module before
> second..
Once merged, the merge module's components become part of the MSI so you
can't control how they're installed.
--
sig://boB
http:
Maybe the easiest solution should be to use two MSM files in one MSI
and with dependencies force to install first MSM module before
second...
I think, this way is according the MSI philosophy...
David.
2007/8/31, Pierson Lee (Volt) <[EMAIL PROTECTED]>:
>
>
>
> Windows Installer will not run two MS
Windows Installer will not run two MSIs at the same time. The only way you're
going to be able to do this is to use a bootstrapper. I ran into the same
problem attempting to deploy a component MSI (.net framework 2.0) within mine
and had to find an alternate method.
From: [EMAIL PROTECTED] [mai
7 matches
Mail list logo
