Hi,
It would be great if the Extract Archives action could be assigned to a specific component (and in turn to a feature) or directly to a feature. In the current way, this is not possible and it can be easily missed that this action is always executed, no matter the chosen build config and in turn the features that are included in the installer. The only way to "assign" it to a feature is by using a condition that checks whether the feature is going to be installed.
If the user builds a configuration that not includes the .zip file, it tries to extract a non-existent file (and in turn shows a failure message that is not helpful at all as it does not contain the path to the specified file) in the worst case. This error is not that easy to locate (due to the imprecise log message) and cost some time to figure out today.
All the best,
Johannes
Suggested Articles
Re: Extract Archives - assign to component
Hello Johannes,
I've had a look over this and I can confirm what you've said.
Being able to tie the action to a component (e.g. the archive's component) would really help here.
I have forwarded this to our development team.
Thank you for bringing this to our attention!
Best regards,
Catalin
I've had a look over this and I can confirm what you've said.
Being able to tie the action to a component (e.g. the archive's component) would really help here.
I have forwarded this to our development team.
Thank you for bringing this to our attention!
Best regards,
Catalin
Re: Extract Archives - assign to component
Hello Catalin,
You're sincerely welcome and thanks a lot, that sounds promising! Looking forward to an improved solution here.
Best regards,
Johannes
You're sincerely welcome and thanks a lot, that sounds promising! Looking forward to an improved solution here.
Best regards,
Johannes