The merge modules coming out of DevDiv have traditionally been, erm, less
than reliable.

For a list of some known faults in the VS6 merge modules, see
http://www.installsite.org/pages/en/bugs_msi.htm#wimsm.

-- 
Mike Dimmick

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Hüseyin
Tüfekçilerli
Sent: 13 December 2007 19:34
To: Bryan C. Boettcher
Cc: WiX-users
Subject: Re: [WiX-users] Problems deploying Microsoft MSM moduleto
SystemFolder

Bryan C. Boettcher wrote:
>
> Sorry about that, Bob.  Mis-click of the reply button.
>
>  
>
> These are the official merge modules from Microsoft for VS6.
>
>  
>
> ------------------------------------------------------------------------
>
> *From:* Bob Arnson [mailto:[EMAIL PROTECTED]
> *Sent:* Wednesday, December 12, 2007 10:49 PM
> *To:* Bryan C. Boettcher; WiX-users
> *Subject:* Re: [WiX-users] Problems deploying Microsoft MSM module to 
> SystemFolder
>
>  
>
> Please keep /wix-users/ on the thread so everyone can participate.
>
> Bryan C. Boettcher wrote:
>
> Well, adding those merge modules also broke other things in the MSI.  Do
version incompatibilities (v2 vs. v3) matter?  We're using v3.
>   
>
>
> It shouldn't, as long as the merge modules are correctly defined.
>
>
> E:\Temp\2yp6kopw\ product.msi : error LGHT0204 : ICE03: Table: Class
Column: CLSID Missing specifications in _Validation Table (or Old Database)
>   
>
>
> I've never seen those before. Where did you get the merge module?
>
> -- 
> sig://boB
> http://joyofsetup.com/
Recently I have faced with the same issue. According to my research, as 
also Bob said, you can ignore the warning LGHT1056, I think it just 
tries to make msi author think twice before deploying into SystemFolder. 
In our case while merging modules like mscomctl, mscomct2, msvbvm6, etc. 
there is not any better directory then SystemFolder IMO.

For error LGHT0204 : ICE03 situation, those merge modules are missing 
validation tables and we are getting those errors/warnings when we merge 
them into our MSIs. You can use EnsureTable 
(http://wix.sourceforge.net/manual-wix2/wix_xsd_ensuretable.htm) tag in 
your wxs file under <Product /> to avoid those and let WiX to generate 
those tables for you.

<EnsureTable Id="Class" />
<EnsureTable Id="Extension" />
....
...

HTH.

-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to