So, I managed to find the core issue. I don't know if this is the right answer but it seems to work.
The problem laid in Light's function of removing unused entities, or not included unreferenced entities. In the example I gave notworking.wxs had included only a FeatureRef link to a Feature element in package.wxs. I swapped the Feature and FeatureRef around so that package.wxs contained a FeatureRef to a Feature element declared in notworking.wxs. Because there was now a direct reference to an element in notworking.wxs the property was also included. Phew! Paul Bates wrote: > > I've been trying to solve this one for at least a full day. I do not > understand why content in a wxs, which is present in the resulting wixobj, > is not linked into an MSI. > > I'm using Votive for development, but that doesn't matter because it > happens on the command line also. In one wxs fragment file > (notworking.wxs) I define a property: > > <property name="TEST_PROPERTY" value="11"/> > > Compile the project and examine the resulting MSI using Orca. The property > is not in the property table so I check the notworking.wxsobj file and > there is the entry. > > <table name="Property"> > <row sourceLineNumber="notworking.wxs*3"> > <field>TEST_PROPERTY</field> > <field>11</field> > </row> > </table> > > I check the command line generated by Votive and the notworking.wixobj > file is included when linking. > > I should point out that I have tried cleaning all wixobj files and MSIs to > ensure that nothing is being persisted between sessions. > > I remove the property from the notworking.wxs file and place in another > file (package.wxs) in the project, check the resulting msi with Orca and > now it's there?! This is strange behavior that I cannot seem to place and > reasoning for. The only difference between the two wxs file is the > non-working notworking.wxs version is placed in a directory two levels > below the working package.wxs file, which is actually the project folder. > So I thought I would copy the notworking.wxs file to the same location but > it still does not work. > > I took to debugging light.exe to see what the problem was but there is > none that I can see. I see the notworking.wixobj file is loaded and the > content added for later processing. > > As a side note, I do not understand, my project used to compile correctly. > I actually created a WiX installer framework for our products. The product > that I'm working on the installer for does not work, however the other > product using a similar layout structure and the same internal tools works > perfectly - on a daily basis?! > > Has anyone else experienced this behaviour or know of a solution? > > I'm using WiX 3.0 > > Thanks for the help, > Paul. > > > -- View this message in context: http://www.nabble.com/Light-is-ignoring-content-in-wixobj-files-tf3521076.html#a9827515 Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
