I've validated my MSM in Orca. At first, I got a lot of ICE33 warnings
because of some COM registration logic. To rule out that this was
causing my problems, I removed this registration logic and validated the
MSM again. Now the validation completes, but ends with:
Execution ERROR There is a problem with this Windows Installer
package. A DLL required for this install to complete could not be run.
Contact your support personnel or package vendor.
I'm using Orca with the darice.cub of WIX 3.6 BETA
Looking further in Orca, I saw 2 tables (ModuleInstallExecuteSequence
and ModuleInstallUISequence) which both contained an action called
AppSearch with a Sequence of 50. I guess the actions of these tables are
moved to the InstallExecuteSequence and InstallUISequence tables when
you embed this merge module into an installer. So could this be the
cause of the warnings I see when I build my installer?
Somewhere in my merge module I perform a registry search to get a
directory from the registry:
<Property Id="MYDIRECTORY">
<RegistrySearch Id="REG_DirectorySearch" Type="raw"
Root="HKLM" Key="Software\MyApplication" Name="InstallDir"/>
</Property>
*MYDIRECTORY is the ID of a Directory element.
When I remove this registry search, the AppSearch actions are also
removed from the 2 tables. And I don't get the warnings anymore when I
build the installer containing this merge module. The original problem,
that a registry key was not written when you run the installer, is also
gone now.
Am I using the RegistrySearch in a correct way? Or is there another way
to fill the Directory element with a value from the registry?
-----Original Message-----
From: Blair [mailto:os...@live.com]
Sent: Monday, January 30, 2012 1:30 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Visual C++ 2010 Merge Module
The only reason I asked is because the guid that suffixes the property
names is supposed to be the MSM's Package @Id, and there should be no
reason that your MSM is using another MSMs properties. However, that
appears to be a red herring (the "duplicate sequence number" warnings
are expected in that scenario). The purpose of the duplicate sequence
warnings is to make you look to ensure that there isn't any sequencing
expectation between the actions being merged. Setting the values of the
system directories doesn't generally have that concern.
The concern I see looking more closely at your build spew is the "action
[that] cannot be merged" report. Are the names of the actions really
blank
('') or did you remove the action names? If you look at your MSM in Orca
(or other MSI viewer/editor), does it really have entries in the
sequence tables with blank or missing action names? Does your MSM pass
validation by itself?
Blair
-----Original Message-----
From: Joost van Zoest [mailto:jzo...@siqura.com]
Sent: Monday, January 30, 2012 12:58 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Visual C++ 2010 Merge Module
If you mean if I've used guids which are also used in the VC MSM, then
no.
I've tested this by generating completely new guids for my merge module,
and still I got the warnings.
Thanks for the idea though, didn't think of this obvious error...
-----Original Message-----
From: Blair [mailto:os...@live.com]
Sent: Monday, January 30, 2012 9:07 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Visual C++ 2010 Merge Module
Did you borrow VC's MSM's package guid for your MSM?
This message contains confidential information and is intended only for
the individual named. If you are not the named addressee you should not
disseminate, distribute or copy this e-mail. Please notify the sender
immediately by e-mail if you have received this e-mail by mistake and
delete this e-mail from your system.
------------------------------------------------------------------------
----
--
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------
------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
This message contains confidential information and is intended only for the
individual named. If you are not the named addressee you should not
disseminate, distribute or copy this e-mail. Please notify the sender
immediately by e-mail if you have received this e-mail by mistake and delete
this e-mail from your system.
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
