Actually the change to my ParseElement code did not resolve the problem and introduced other xsd validation problems. I reverted back to xsd which does not include the xs:appinfo/xse:parent. I can see in the Wix Extensions that xse:parent is used to declare multiple possible parents, which is useful, but I don't see what I am doing wrong yet. Still researching this issue.
-- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/CompilerExtension-xsd-tp7598978p7598985.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users