From: SourceForge.net <no...@so...> - 2004-07-29 22:11:44
|
Bugs item #964895, was opened at 2004-06-02 02:46 Message generated for change (Comment added) made by robmen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642714&aid=964895&group_id=105970 Category: candle Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Kalle Olavi Niemitalo (kal-le) >Assigned to: Rob Mensching (robmen) Summary: FeatureRef imposes an ordering on children, unlike Feature Initial Comment: According to the schema of WiX 2.0.1727.0, the Feature element allows ComponentRef, MergeRef, FeatureRef, and Feature as its children. These elements can be in any order. However, the children of a FeatureRef element must always be in this order: Feature, ComponentRef, MergeRef. This seems inconsistent to me. I had a Feature that contained a MergeRef followed by a number of ComponentRefs. Now that WiX 2.0.1727.0 allows MergeRef in FeatureRef, I tried to replace the Feature element with a FeatureRef and define the actual Feature elsewhere. However, I got an error from the first ComponentRef in the MergeRef: fatal error CNDL0027: The element 'FeatureRef' has invalid child element 'ComponentRef'. Expected 'MergeRef'. I could work around this error by moving the MergeRef element below the ComponentRef elements. ---------------------------------------------------------------------- >Comment By: Rob Mensching (robmen) Date: 2004-07-29 15:11 Message: Logged In: YES user_id=991639 Fixed in 1927, now using choice instead of sequence (like we should have from the beginning) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642714&aid=964895&group_id=105970 |