Hi,
I would like to enter a license key for my installer to control which
features are visible to the user. I have created a UI page for entering the
key and can successfully control some properties to identify which features
should be available. The problem I have is that using condition elements for
the features based on these properties (set from a CA fired from the page)
do not have any impact as the feature list has already been constructed by
this point. Any way around this?
If I solve this, and work out how to make it work for a silent install, I
would like to save the key in the registry so that later change / repair /
remove use of the MSI does not require the key to be entered again. This is
easy enough, but I'd also like the option to allow a user to enter a new
license key at this point to 'unlock' other features - which would of course
require saving the new key over the old one - I assume if two features
reference the same component which creates a registry key, the latter
wouldn't update the existing key's value as it would see it as already
installed?
Thanks
Nick
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
