Well, A merge module is very similar in structure to an Installer package.
The major difference is that it doesn't contain everything a complete package
holds so that the component can't be installed by the Installer just by using
the merge module. The merge module contains the tables and binary
hi,
can any one explains me, how merge modules will work?
Thanks,
Phani
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and fo
Hi Rafi,
If you're primarily using WiX for all your installs, using
compone...@guid='*'] will cause your component guids to be generated
as a hash of the target path... So, provided the target paths line up
based on your directory structure in your source, all the GUIDs should
come out generated i
Hello,
Our build system generates two separate .wxs files (and therefore two
installers) dynamically dependent on our deployment directories - think about
it as two products/installers that can run independently, but can 'talk' to
each other.
By default, both of these installers install int
Is there anyway to push in a fragment at link time without the main
WXS file containing explicit references to elements in the fragment?
I've got many wxs sources generated at build time that I'd like to not
muck about with. I was hoping that I could include a CA and some
properties simply by lin
Hello,
I am trying to build an installer for a .Net COM dll - and the things seem to
work until the developer tries to use the COM object. If the developer runs
regasm and gacutil on the dll then she is then able to use the COM object.
I was under the impression that my MSI installer should hav
I'm curious why you do it this way. InstallShield has Product Configurations
and Release Flags that would alow you to build MSI's in various ways to address
the variation points you describe. A limitation would be if you wanted to have
the same feature tree but different module inclusions but
Basically MsiPubAssemblies runs in commit phase execution so regardless of
where you schedule it, you'll have this race condition.
http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg12694.html
Have you considered using COM extraction instead of SelfReg? Since
DllRegisterServer does
Hi,
I have a few self-registering ocx:es which depend on Microsoft CRT dlls
(msvctrt.dll). I include Microsoft_VC80_CRT_x86.msm in my msi.
However, when my ocx self-registers during installation, the CRT dlls are not
available yet. I saw that the MsiPublishAssemblies action is scheduled after
S
Hi All,
In a dialog we are trying to populate few of the databases in a ComboBox...
Its working fine , and its showing databases in the combo
The code is below inside a custom action written in C#.
foreach (string database in databases)
{
Record lRecord =
Thanks for your response.
I may have started to handle the issue from the wrong side:
My project consists of several merge modules created with WiX and a "main"
package, which is actually authored with InstallShield. The merge modules are
not addressed in the InstallShield project, so I first b
Any ideas? Anyone?
What direction to dig to troubleshoot this?
-- Yan
-Original Message-
From: Yan Sklyarenko [mailto:y...@sitecore.net]
Sent: Monday, September 07, 2009 11:20 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] HttpHeader doesn't handle
As you say the Module element doesn't seem to have the Media child
element (http://wix.sourceforge.net/manual-wix3/wix_xsd_module.htm) but
it doesn't really matter. When the merge module is consumed into an MSI
its files will be compressed into the media table of the MSI and
therefore use the same
13 matches
Mail list logo
