Harvesting projects with Heat missing KeyPath

Question

Could someone please educate me as to why, when I harvest a project using 'heat project' command it doesn't set the KeyPath attribute on any of the files?

heat project MyApp.csproj -Configuration Release -pog Binaries -pog Content -pog Satellites -ke -directoryid MyAppDir -gg -g1 -out D:\MyApp.wxs

In the output, I have 1 file per component so I don't understand why it doesn't set it. I've used 'Heat dir' for some 3rd party libraries that's fine.

I'm sure there's a good reason, but I'm fairly new to WiX and there doesn't seem to be a great deal of info.

Please put me out of my misery.

thanks

Wim Coenen · Accepted Answer · 2012-03-22 12:28:19Z

4

I have 1 file per component so I don't understand why it doesn't set it

When you have a wix Component element with one file, that file automatically becomes the keypath of the component. It is not necessary to specify it explicitly. You can verify this by opening the produced MSI file with orca and examining the KeyPath field in the Component table.

This behavior is described in the documentation of the KeyPath attribute for the Component element.

edited Mar 22, 2012 at 12:28

answered Mar 22, 2012 at 12:11

Wim Coenen

67k14 gold badges162 silver badges253 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

lyona Over a year ago

I see, that makes sense thanks. But is there a reason for the different behaviour of Heat project and Heat dir with respect to explicitly specifying KeyPath?

Collectives™ on Stack Overflow

Harvesting projects with Heat missing KeyPath

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related