This documentation is archived and is not being maintained.

Unable to build custom action named '<name>' because it uses a conditionally installed file

The specified custom action cannot be built because the file containing the custom action has its Condition property set in the File System Editor. Custom actions are run at the end of installation and must be available on the target computer or the installation will fail and be rolled back; conditionally installed files might not be available.

Conditions can be set for custom actions using the Condition property in the Custom Actions Editor; they cannot be set in the File System Editor.

To correct this error

  1. Double-click the error message in the task list to go to the file containing the custom action in the File System Editor.
  2. In the Properties window, select the text in the Condition property and choose Cut from the Edit menu.
  3. In the Custom Actions Editor, select the referenced custom action.
  4. In the Properties window, select the Condition property and choose Paste from the Edit menu.

See Also

Condition Property | Custom Actions Management in Deployment

Show: