Upon further review... The requirement is to support multiple instances of my product on the same machine. There is a related product that uses InstallShield for their packaging. I need to allow the person installing the product to pick one of those instances. I just need to read the registry, retrieve the location of that instance so that I can customize the default shortcuts with that information.
The more I thought about this the more I realized that this should be done in the bootstrapper. I am going to implement my own bootstrapper that does this. I will then pass the customization in via property values to control the behavior of the installation. This might mean that I cannot use setupbld.exe to embed my generated msi file into my own setup.exe instead of using the WiX supplied setup.exe. I really like using setupbld.exe to generate a single package but if that will not be possible with my own setup.exe that it will not be the end of the world. Thanks for creating the WiX project! Durwin Wright | Sr. Architect | durwin.wri...@ingres.com | Ingres | 500 Arguello Street | Suite 200 | Redwood City | CA | 94063 | USA +1 650-587-5523 | fax: +1 650-587-5550 | "Wag the Dog" -----Original Message----- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Tuesday, July 13, 2010 4:58 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Obtaining Enumerated List of Registry Entries andDisplaying them in a selection list Nothing built in. Never heard of that requirement before. Why do you need to do that? On Mon, Jul 12, 2010 at 8:51 PM, Durwin Wright <durwin.wri...@ingres.com>wrote: > Hello, > > I have started to use WiX 3.0 to begin our transition away from > InstallShield. I really like using it. > > I have a question that may or may not be obvious... > > We have a requirement to get a list of registry keys under a parent key, > and display information to the installer. There is a possibility of > over a thousand registry keys (most of the time there will be less than > three or four). Is there a way to do this simply in WiX or will I need > to resort to a DLL and Custom Action? > > I really appreciate any responses. > > Thanks. > > Durwin Wright | Sr. Architect | durwin.wri...@ingres.com | Ingres | 500 > Arguello Street | Suite 200 | Redwood City | CA | 94063 | USA +1 > 650-587-5523 | fax: +1 650-587-5550 | "Wag the Dog" > > > > ------------------------------------------------------------------------ ------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC ------------------------------------------------------------------------ ------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
