Please post a message with more details about your problem to wix-users.

The normal install works fine but the patching process is a nightmare and I’m thinking about just using that and giving up on patching – it has been is a whole world of hurt, although ironically I’m probably one setting away from suceeding! When I change

to set Compressed=”no” then I get the following error:

The cabinet ‘WixMinimalSample.cab’ does not contain any files. If this installation contains no files, this warning can likely be safely ignored. Otherwise, please add files to the cabinet or remove it.

When it’s set to “yes”, I get a full install which works nicely.

any ideas?

regards
ewart

Thank you for all your help. The heat switch worked perfectly together with a ComponentGroup/Ref (I noticed that heat.exe has some new info when using /?, very nice).

To be honest, if you’re using Heat, I’d use the -sfrag switch to create one fragment per harvest; when you do that, it also generates a ComponentGroup that you can use to pull in all the components with one ComponentGroupRef element. Otherwise, you’ll need one reference for every fragment.

How then is the easiest way to include a file with components (I have one for each feature in my installation) into your “main” WiX-file that contains the Product element? Using some kind of include in the main WiX-file?

The sample you posted works as expected; the problem is that nothing in your Product section references anything in the Heat-generated Fragment so the linker doesn’t include the fragment in the output. References start in the entry section (Product, in this case) and go down; a reference from a fragment into the entry section doesn’t cause the fragment to be included (though once it is, those references resolve correctly).

As Derek told me when I ran into the same problem: “Parents can pick their children, but children can’t pick their parents.”

You can see the same problem if you were to use FeatureRef in your Heat-generated fragments (which is roughly what Component/@Feature does).

thank you for your reply. I have created a bug (http://sourceforge.net/tracker/index.php?func=detail&aid=1885447&group_id=105970&atid=642714) and assigned it to you.

I think have narrowed it down to using the Feature attribute on Heat-generated Components (that is, contained in Fragments and within DirectoryRef elements), since it works if I use a Feature attribute on a Component element directly below a Directory element.

I can’t reproduce that on my machine. I’ll take a look with 3725 over the weekend but in the meantime, try this sample (you’ll need fudge the files it’s including). I get no ICE warnings/errors and the File and Media tables look fine:

Edit: OK, that’s not going to work — WP doesn’t much like my pasting in XML into the comment editor. If you open a bug with your sample, I can attach mine to it.

However, if I use a ComponentRef under the Feature element instead, it works.

However, the Feature attribute seems to be used for something, because if specify the Feature attribute on a Component AND use a ComponentRef under the Feature, I get the error “The primary key ‘MyFeatureId/MyComponentId’ is duplicated in table ‘FeatureComponents’. Please remove one of the entries or rename a part of the primary key to avoid the collision.”

Any hints?