Windows Installer Editor Reference
261
Advanced Installations
Specifying Replacements in SQL Statements
You can specify text strings to be found and replaced within the SQL statements during
installation.
To specify replacements in SQL statements
1. Click the Replacement tab on the SQL Script Details dialog box.
See
Configuring a Microsoft SQL Server During Installation
on page 257.
2. Click Add.
The Add Replacement dialog box appears.
3. Complete the dialog box:
Text to Find
Enter regular text or formatted text, such as a bracketed property name. If you
enter formatted text, it is resolved before the find and replace takes place.
Example: If you enter [INSTALLDIR], the find and replace searches for the
value of INSTALLDIR.
Replace With
Enter regular text or formatted text, or select a current Windows Installer
property from the drop-down list. If you enter formatted text, items are
replaced with the value of the formatted text. This is useful for creating dynamic
installations. Example: Suppose you are creating a new database on the server.
Place an edit field on a dialog box asking for the new database name. The
answer is stored in a property, which you could then use in this field, replacing
the current database name.
4. Click OK.
Note
Keep in mind that any matching string is replaced, so only replace strings you know to
be unique. Example: If you replace “Red” with “Blue,” a “PreparedStatement” object in a
SQL statement becomes “PrepaBlueStatement” and breaks the code.
See also:
Tips for Using the SQL Server Scripts Page
on page 258
Importing .NET Framework Security Settings
Use the .NET Framework Security page to import .NET Framework security settings from
your computer into an installation for a .NET application that you are deploying using
no-touch deployment. No-touch deployment lets system administrators deploy .NET
desktop applications through a remote Web server without altering the end user’s
registry or shared system components. Search for “No-Touch Deployment in the .NET
Framework” in the MSDN Library (
msdn.microsoft.com/library/
).
When an end user downloads your .NET application using no-touch deployment, they
need specific security settings to be able to run the application. You import these
security settings from your computer into the installation. When the application is
downloaded, the settings you imported into the installation change the client’s security
settings and enable the application to run.
