If an extension library contains custom actions that are meant to be "manually" referenced via CustomActionRef (for example, instead of via compiler extension authoring) and the DecompilerExtension.RemoveLibraryRows property is true (the default), the decompiler will omit any reference to the CA or its scheduling. If the library included the CustomAction row but not a matching InstallExecuteSequence row, this problem manifests as a DARK1024 warning. If the library includes both, the CA and schduling are entirely omitted without warning.
A decompiler extension can be written to look for known CA names and emit the authoring anyway but a more elegant way of telling Decompiler to keep those rows would be nice.
If an extension library contains custom actions that are meant to be "manually" referenced via CustomActionRef (for example, instead of via compiler extension authoring) and the DecompilerExtension.RemoveLibraryRows property is true (the default), the decompiler will omit any reference to the CA or its scheduling. If the library included the CustomAction row but not a matching InstallExecuteSequence row, this problem manifests as a DARK1024 warning. If the library includes both, the CA and schduling are entirely omitted without warning.
A decompiler extension can be written to look for known CA names and emit the authoring anyway but a more elegant way of telling Decompiler to keep those rows would be nice.
bq. Originally opened by @barnson@ from "http://sourceforge.net/p/wix/feature-requests/380/":http://sourceforge.net/p/wix/feature-requests/380/