VS2010/Votive displays bal:Overridable as an attribute option for
Bundle/Chain/MsiPackage.  While I did not find this attribute documented in
the Schema for MsiPackage (as it is for the Variable element) I wondered if
I could set it and then (just guessing) pass a property on the command line
to my WixStdBA and see if that property got added to this MsiPackage's
property list or the msi's command line.  (I am aware the I can define a
Variable with bal:Overridable and use the variable to set a MsiProperty, but
I wondered why the bal:Overridable was offered as an attribute to
MsiPackage.)

When MsiPackage/@bal:Overridable="yes" if provided the following compile
error is observed:
"
C:\Program Files (x86)\WiX Toolset v3.7\bin\candle.exe -dDebug -dDEBUG
-d"DevEnvDir=c:\Program Files (x86)\Microsoft Visual Studio
10.0\Common7\IDE\\" -dSolutionDir=<project path>\ -dSolutionExt=.sln
-.......<wix tools>\WiX Toolset v3.7\bin\\WixBalExtension.dll" file1.wxs
file2.wxs file3.wxs file4.wxs file5.wxs
                Windows Installer Xml Compiler version 3.7.1224.0
                Copyright (C) Outercurve Foundation. All rights reserved.
                file1.wxs
                file2.wxs
                file3.wxs
<path to >file3.wxs(76,0): error CNDL0005: The MsiPackage element contains
an unexpected child element 'MsiPackage'.
                file4.wxs
                file5.wxs
Done building project "QDsetup.wixproj" -- FAILED.
"

When I remove the MsiPackage/@bal:Overidable="yes" then the project compiles
and runs as expected.  So I will leave this experiment alone and implement a
Variable/@bal:Overidable to address my need pass a property to the msi
package.  But I wondered if this error message made sense to anyone?



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Chain-MsiPackge-bal-Overridable-yes-yeilds-strange-error-tp7587767.html
Sent from the wix-users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to