We have 2 versions of our product that install either integrated with VS or to use the isolated shell. One project allows us to set a custom action deferred with no impersonation, and the other project will not allow us to do this as this option is greyed out. Is there a reason why a project would NOT allow you to set a custom action as deferred? The custom actions are identical and are executing an installed file with a command line.
Thanks!
AJ
Suggested Articles
-
mcseforsale
- Posts: 57
- Joined: Wed Mar 27, 2013 10:53 pm
-
mcseforsale
- Posts: 57
- Joined: Wed Mar 27, 2013 10:53 pm
Re: Cannot set custom action as deferred
This is fixed. It was an issue with our build machine.
Re: Cannot set custom action as deferred
Hello,
I'm glad you sorted things out.
Please note that a custom action can be set as deferred only if it is scheduled as a custom action with sequence anywhere after the "Install Execution Stage" -> "Preparing" action group and "Install Executions Stage" -> "Finish Execution Stage" action group. Scheduled anywhere else it cannot be executed as deferred.
All the best,
Daniel
I'm glad you sorted things out.
Please note that a custom action can be set as deferred only if it is scheduled as a custom action with sequence anywhere after the "Install Execution Stage" -> "Preparing" action group and "Install Executions Stage" -> "Finish Execution Stage" action group. Scheduled anywhere else it cannot be executed as deferred.
All the best,
Daniel