One workaround that I can think of right now is to: 1. Create a dummy script in the Installation Designer and the script will contain only a placeholder for text replacement. 2. Configure the Text Replacement to replace that placeholder with an installer property. 3. Create a custom action that, during the installation, reads the content of the "extra\custom.sql" and store it in that installer property. But i'm afraid the content of custom.sql might be too large for an installer property to hold. ... View more