#1343 Need better error message: Registry/KeyPath/Action

[J Gionta]

I recently update to the latest version of Wix (3.0.43) from version 3.0.29 to get a fix regarding FindIIsWebs custom action. However, now my candle command fails regarding Registry nodes.

I receive an error saying that a Registry object cannot have an Action value of '' when KeyPath is set. In my Wix script I do no have an Action attribute. So it seems anytime I have a registry node with a KeyPath attribute, candle fails because it thinks there is an action attribute.

Thanks for any help.

Here is a log snippet:

error CNDL0035 : The Registry/@KeyPath attribute cannot be specified when attribute Action is present with value ''.

[Bob Arnson]

Please post your Registry element so we can see what's causing the message. Also note that in WiX v3, Registry is deprecated in favor of RegistryKey/RegistryValue.

[J Gionta]

Thanks Barnson for the quick response. I know that registry is deprecated, thats why I'm even more baffled something changed.

<registry root="HKCU" key="SOFTWARE\Microsoft\.NETFramework\AssemblyFolders\Monitor_Exe" keypath="yes"></registry>

Thanks again.

[Bob Arnson]

We need to improve the error message but it's actually catching something bad that WiX v2 allowed. Only registry values, not keys, can be key paths. (It might work to use the key's default value.)

[SourceForge Robot]

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 15 days (the time period specified by
the administrator of this Tracker).