Re: [WiX-users] Preprocessor and Component Guids

2009-08-31 Thread Blair
aillet, Ed [mailto:email...@unum.com] Sent: Monday, August 31, 2009 9:59 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Preprocessor and Component Guids Here's the real use case. I need to create what I'll call an 'Infrastructure Package', specifically for a web serv

Re: [WiX-users] Preprocessor and Component Guids

2009-08-31 Thread Blair
No keypath in your component? You are likely to have a hard time with upgrades and servicing if you don't come up with a way to make your generated guids consistent from build-to-build for the same inputs. I would recommend you make a series of RegistryValues (one for each "component") and use the

Re: [WiX-users] Preprocessor and Component Guids

2009-08-31 Thread Maillet, Ed
Message: 7 Date: Mon, 31 Aug 2009 16:25:46 + From: Svet Bonev Subject: Re: [WiX-users] Preprocessor and Component Guids No, there is no built-in functionality to accomplish that. But the bigger question is why you want to create such components. Ideally, you would have file KeyPaths. Ran

Re: [WiX-users] Preprocessor and Component Guids

2009-08-31 Thread Svet Bonev
No, there is no built-in functionality to accomplish that. But the bigger question is why you want to create such components. Ideally, you would have file KeyPaths. Random component guids are usually bad for servicing scenarios. What are you doing with these components? Giving us more details