I was coming to the same conclusion myself that just editing the MSM would be
the simplest solution - it is written using InstallShield and uses their
ISSeflReg table which I don't like but is easy to fix.
Neil
Neil Sleightholm
X2 Systems Limited
[email protected] <mailto:[email protected]>
________________________________
From: Svet Bonev [mailto:[email protected]]
Sent: Wed 04/11/2009 05:38
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Ref File Id in a merge module
Are you consuming the merge module through Merge/MergeRef?
If so, you wouldn't be able to get past this error - merge modules are
processed as part of the binding phase of the WiX build process which is well
after linking -- where you got the error.
I can suggest you two approaches:
1) Modify the merge module itself with Orca or another MSM editor and add the
appropriate row to the Class table.
or
2) Keep the Class element; use melt.exe to decompile the module to a
ComponentGroup and switch your MergeRef to ComponentGroupRef to include it.
FWIW, this method is more complicated than the 1st one and if you get the fix
you need it may turn out to be throwaway work, but it lets you service the MSM
through WiX 3.0 style patching against wixpdbs and not using admin image
patching.
Svet
________________________________________
From: Neil Sleightholm [[email protected]]
Sent: Tuesday, November 03, 2009 12:22
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Ref File Id in a merge module
I have a merge module that was supplied to me but it has a bug in it
that means it doesn't register a com component. I am hoping to get a fix
for this but I thought I should be able to fix the problem by adding the
relevant registry keys to the host install. I have added a component and
have added <Class> element like this:
<Class Id="{.....}" Context="InprocServer32" Server="filename.GUID"
...... >
filename.GUID is the file id from the merge module with the module guid
appended. When I build this I get the error:
"Unresolved reference to symbol 'filename.GUID' in section 'Product:*'"
I have checked the guid and I am fairly sure it is correct (I ran dark
on the merge module and read the Package/@Id and the relevant File/@Id).
Can anyone tell me if this should work? If it should can you suggest how
to make it work?
Thanks
Neil
Neil Sleightholm
X2 Systems Limited
[email protected] <mailto:[email protected]>
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
