I also figured out the real problem and solution to my xsd. Since I had not
defined each element at the root (global) level I was getting a variety of
xsd parsing problems. One I understood that concept I was able to create a
xsd which follows the pattern of xsd files found in the other Wix
Exten
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 use
I found the problem in my ParseElement implementation. Thanks.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/CompilerExtension-xsd-tp7598978p7598981.html
Sent from the wix-users mailing list archive at Nabble.com.
--
3 matches
Mail list logo
