I suspect your original UI refs contain a welcome dialog. The FeatureTree UI is a complete UI. Its not just a FeatureTree dialog so the combination of your UIrefs and FeatureTree means you have duplicate dialogs, hence the error.
If the standard feature tree UI sequence work for you as is, then remove your other UIrefs and just use FeatureTree on its own. If you use a custom UI sequence then your only option, I think, is to add the individual dialogs you need to your custom UI. You won't be able to use WixUI_FeatureTree as is. Chris On 08/11/2010 03:28 PM, little.forest wrote: > Hi Chris, > > > Thanks. Yes, I have UIRef before I added the new FeatureTree: > <UIRef Id="MyWixUI_InstallDir"/> > <UIRef Id="WixUI_ErrorProgressText"/> > > > > > > ________________________________ > From: Chris Lord<chris.l...@atterotech.com> > To: General discussion for Windows Installer XML toolset. > <wix-users@lists.sourceforge.net> > Sent: Wed, August 11, 2010 12:22:40 PM > Subject: Re: [WiX-users] How to add FeatureTree > > Did you already have a UIRef in your wxs before you added the > FeatureTree UIRef? > > > On 08/11/2010 03:00 PM, little.forest wrote: > >> We'll need to add a new component. And we'd like the end user to choose to >> install it or not. >> >> I found the FeatureTree maybe a fit for us. So I add these code: >> <UIRef Id="WixUI_FeatureTree"/> >> >> >> <Property Id="INSTALL_FEATURE1" Value="1" /> >> >> >> <DirectoryRef Id='INSTALLLOCATION'> >> <Component Id='COMP_FTR1' Guid='*'> >> <File Source='feature1.dll' KeyPath="yes" Checksum="yes" /> >> </Component> >> </DirectoryRef> >> >> <Feature Id='Feature_1' AllowAdvertise='no' Description='This is for feature >> > 1' > >> Title='New feature 1' Level='2'> >> <Condition Level='1'>INSTALL_FEATURE1</Condition> >> <ComponentRef Id='COMP_FTR1' /> >> </Feature> >> >> >> But I'm getting this error when compiling: >> error LGHT0130 : The primary key >> 'LicenseAgreementDlg/Back/NewDialog/WelcomeDlg/1' is duplicated in table >> 'ControlEvent'. Please remove one of the entries or rename a part of the >> primary key to avoid the collision. >> >> How can I fix it? >> >> Thanks all. >> >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by >> >> Make an app they can't live without >> Enter the BlackBerry Developer Challenge >> http://p.sf.net/sfu/RIM-dev2dev >> _______________________________________________ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
