Features are selected or unselected for install depending on the INSTALLLEVEL value not whether their Level attribute is even or odd. See http://msdn.microsoft.com/en-us/library/aa369536.aspx
A verbose log should tell you what's happening with the default states of your Features. Palbinder Sandher Software Deployment & IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the <Virtual Environment>** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -----Original Message----- From: Rune Moberg [mailto:jjfl...@gmail.com] Sent: 23 January 2011 21:16 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Feature not pre-selected I have a bunch of features. Some of them do not contain any file resources, they're just there as a convenience to help the customer get a few services up and running. Given: <Feature Id="ProductFeature" Title="Mikromarc server" ConfigurableDirectory="MIKROMARC3ROOT" Level="1" Absent="disallow" Display="expand"> <ComponentRef Id="Dependencies"/> <Feature Id ="Messages" Title="Messages service" Description="Registers the Messages service." Level="1"> <ComponentRef Id="MsgExe"/> </Feature> <Feature Id="Cbc" Title="Common borrower card" Description="Registers the common borrower card service." Level="1" TypicalDefault="install" InstallDefault="local"> <ComponentRef Id="CbcExe"/> </Feature> <Feature Id="MM2" Title="MM2 Conversion utility" Description="An utility for converting old Mikromarc 2 databases." Level="2"> <ComponentRef Id="MM2Convert"/> <ComponentRef Id="MM2ConvertCfg"/> </Feature> </Feature> I expected that "MM2" would be deselected in the CustomizeDlg. And indeed it is. What I do not understand is why the "Cbc" feature is not selected? I thought that an even value for Level would deselect the item. This seems to fly well with feature "MM2", but has no effect on the "Cbc" feature. I then tried filling its associated component with some proper files, but no difference. <Component Id="CbcExe" Guid="eefccd74-166e-4141-a5fb-80ebf78dc1f7"> <CreateFolder/> <ServiceInstall ... /> <ServiceControl ... /> </Component> is what I have there, but adding a <file> does not help. (The reason I went down that path is that I have two <Component>s defined in this fashion, so I suspected an optimizer realized they were very similar... Given that <file> did not help, I guess this is not the case) -- Rune ------------------------------------------------------------------------ ------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
