John Ludlow wrote:
> An alternative way would be to set properties based on the user input,
> and use elements to control the feature state.
Feature conditions are evaluated during InstallValidate; if you use
public properties, they'll take effect during the execute sequence but
the UI won't r
Don Tasanasanta wrote:
How would you go about enabling or disabling a feature dependant on
input provided by the user on a previous input screen?
Publish AddLocal and Remove control events in the Next button of the
wizard page before the feature-selection page.
--
sig://boB
http://bobs.o
2 matches
Mail list logo