Thanks for the very detailed answer, Mike. I'll add a note to the
tracker case you referenced.
The other solution, which I already implemented, is to include the
missing module in the product merge as well. It was slip on the
original build-writer's part in the first place.
I was just wondering what <Dependency> did if not flag missing
dependencies.
Thanks
Mark
________________________________
From: Mike Dimmick [mailto:[EMAIL PROTECTED]
Sent: Monday, January 28, 2008 5:36 PM
To: mark.modrall; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] newbie question
If you're merging modules written in WiX, and those modules are not
shipped separately to third parties, consider rewriting them as
Fragments. You can precompile a fragment into a .wixout file and simply
link those together. You can assemble one or more .wixout files into a
larger chunk of functionality as a .wixlib using the lit tool. Light
will only include those Fragments in the final MSI which are referenced.
For WiX 2.0 you will need to keep the files to be included around as
loose files; WiX 3.0 can include them in the .wixlib. Light is much more
rigorous than the merge tool.
It looks like the client of the merge library is supposed to use the
Dependencies property (get_Dependencies method) to find out whether
there were any unsatisfied dependencies, but as far as I can see, the
binder does not do that. Indeed WiX 2.0.5325.0's handling of the Errors
collection is commented out. (This is fixed in WiX 3.0.)
I was going to suggest adding this to the bug tracker at
http://sourceforge.net/tracker/?group_id=105970&atid=642714 but I see
that there already is one
(http://sourceforge.net/tracker/index.php?func=detail&aid=1657736&group_
id=105970&atid=642714), although that's for WiX 3.0. It may be worth
adding your note to it as well. Having said that, the aim is to only fix
serious bugs in version 2.0.
--
Mike Dimmick
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
mark.modrall
Sent: 28 January 2008 16:19
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] newbie question
Hi...
I've inherited a build system that does its msi packaging with wix
2.0. Since I inherited the build system, I've also inherited the
complaints about it. While investigating one of them I ran into
something that struck me as odd, and I was hoping someone here might
comment on it.
The final Product.wxs file pulls together all of the component
projects and bundles them into one msi. There are a lot of
<Merge Id="Module1" ... />
<Merge Id="Module2" ... />
...
in the config.
One of the modules projects has a
<Dependency RequiredId="Module27" RequiredLanguage="1033" />
line in it.
The peculiar thing (to me) is that Product.wxs doesn't merge in
Module27 yet there are no warnings or errors about missing dependencies,
either in the Wix solution build nor in the resulting msi. The msi
produced puts all the pieces it has in place; it's just missing one so
the result doesn't work.
Do <Dependency> lines have a function other than a loose kind of
note-taking?
Thanks
Mark
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
