[WiX-users] append to registry

2008-02-19 Thread Jason Rivers
Hi all.

we have a registry string WS for our work spaces, but this should be
modified depending on features that's installed.

for instance, we always want it to read [INSTALLDIR] but if Feature 1 is
installed, then they key should be [INSTALLDIR];[INSTALLDIR]\feature1
again, if Feature2 is installed it should be
[INSTALLDIR];[INSTALLDIR]\feature2 and then if both 1 and 2 are installed
it should read [INSTALLDIR];[INSTALLDIR]\feature1;[INSTALLDIR]\feature2

is this possible to do? we're currently using a custom action to do this,
but it's messy and it means the string isn't removed on uninstall unless we
have a custom action to do that too.

Jason
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] append to registry

2008-02-19 Thread Bob Arnson
Jason Rivers wrote:
 I would maybe do this - but the way the product is setup (and has been 
 for years) is this registry setting, I'm trying to avoid changing the 
 functionality of the product, the registry is there for application 
 settings, this is an application setting. If there's no way to do this 
 within WiX i'll stick to the custom action dll that gets the features 
 and builds the variable - it's just more of a pain this way.

If it's not an environment variable, then no, WiX/MSI doesn't have 
append/prepend support, except for REG_MULTI_SZ strings.

-- 
sig://boB
http://joyofsetup.com/



-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] append to registry

2008-02-19 Thread Jason Rivers
I would maybe do this - but the way the product is setup (and has been for
years) is this registry setting, I'm trying to avoid changing the
functionality of the product, the registry is there for application
settings, this is an application setting. If there's no way to do this
within WiX i'll stick to the custom action dll that gets the features and
builds the variable - it's just more of a pain this way.

Jason


On Feb 19, 2008 3:45 PM, Bob Arnson [EMAIL PROTECTED] wrote:

 Jason Rivers wrote:
  for instance, we always want it to read [INSTALLDIR] but if Feature
  1 is installed, then they key should be
  [INSTALLDIR];[INSTALLDIR]\feature1 again, if Feature2 is installed
  it should be [INSTALLDIR];[INSTALLDIR]\feature2 and then if both 1
  and 2 are installed it should read
  [INSTALLDIR];[INSTALLDIR]\feature1;[INSTALLDIR]\feature2
 
  is this possible to do? we're currently using a custom action to do
  this, but it's messy and it means the string isn't removed on
  uninstall unless we have a custom action to do that too.

 That's bad karma.g The Environment/@Part attribute lets you append or
 prepend values. I'd use three Environment elements in three components:
 one that's included in any/all features, one in Feature1, and one in
 Feature2.

 --
 sig://boB
 http://joyofsetup.com/



-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] append to registry

2008-02-19 Thread Bob Arnson
Jason Rivers wrote:
 for instance, we always want it to read [INSTALLDIR] but if Feature 
 1 is installed, then they key should be 
 [INSTALLDIR];[INSTALLDIR]\feature1 again, if Feature2 is installed 
 it should be [INSTALLDIR];[INSTALLDIR]\feature2 and then if both 1 
 and 2 are installed it should read 
 [INSTALLDIR];[INSTALLDIR]\feature1;[INSTALLDIR]\feature2

 is this possible to do? we're currently using a custom action to do 
 this, but it's messy and it means the string isn't removed on 
 uninstall unless we have a custom action to do that too.

That's bad karma.g The Environment/@Part attribute lets you append or 
prepend values. I'd use three Environment elements in three components: 
one that's included in any/all features, one in Feature1, and one in 
Feature2.

-- 
sig://boB
http://joyofsetup.com/



-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users