> As for the custom action and setproperty. I'd recommend adding a call > to the custom action via the <controlconditions> element. That way, > you can be sure that the custom action is run after the properties are > set. When are you specifying for your custom action to run, now?
How do I specify a custom action to be run from <controlconditions>? When I run the installation I get a dialog that prompts me for the user name and password which should also set properties. Then I see the custom actions being called one by one. The last thing that happens during installation is the custom action called that depends on the user name and password that was entered in the dialog. Chronologically I can tell that the dialog is called first and the custom action is called last. There doesn't seem to be a question of the order right now. Also, I don't think it will work to have the custom action run from <controlconditions> because I am changing the credentials (the account) that the services are run from so the services need to be installed. It is not enough for the properties to be set I need the custom action to run after the services have been run. I have a large number in the the sequence table that seems to run the custom action after the services have been installed. The custom action has no trouble finding the service it is just the properties that should have been set from the dialog seem to be blank. Kevin ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ NAntContrib-Developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nantcontrib-developer
