Search for scripts in staging directory, not current directory

[PaulStovell]

Tentacle always extracts the package to a generated staging folder, such as:

C:\Apps\Environment\PackageName\1.0.0

When customers use the custom installation directory option, they can have the files copied to another location during deployment:

C:\MyApp

In the past, when invoking PowerShell scripts, we used to search the generated staging folder for scripts, then see if they existed in the target directory before invoking. But recently during refactoring this was changed so that we search under the target folder instead. Since the target folder may contain a lot more files, this search can take much longer.

We should revert this to the old behaviour.

[PaulStovell]

Fixed in 2.4

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.