Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>If you don't want the user to change the virtual directory you can simply remove the "Installation Address" dialog from the User Interface.</p> <ol> <li>Right Click installer project and select "User Interface". </li> <li>Expand the "Start" node. </li> <li>Right click on "Installation Address".</li> <li>Select "Delete"</li> </ol> <p>If you want different parameters for the Web site, virtual directory, application pool that is normally selected by the installation address dialog you can override with a custom action as others have described.</p> <p>However, in my experience custom actions do not help with setting defaults that the user can change because they execute <strong><em>After</em></strong> the dialogs that ask for user input.</p> <p>The easiest way to set some defaults that the user can override if necessary in a dialog is to do the following. </p> <ol> <li>Remove the Welcome Page.</li> <li>Add a Textboxes dialog (for example "Textboxes (A)")</li> <li>Change Visible properties for all the textboxes to false so no textboxes are shown.</li> <li>Change the BannerBitmap and BodyText property so it looks somewhat like a welcome page.</li> <li>Set the necessary properties you want to override in the "Edit***&lt;n&gt;<strong><em>Property" and set the default value in the "Edit</em></strong>&lt;n&gt;***Value".</li> </ol> <p>The most useful properties (IMHO) are.</p> <p>TARGETDIR - Where the files are to be copied.<br> TARGETVDIR - The Virtual Directory to be created in the specified site.<br> TARGETAPPPOOL - The application pool to use (NOTE: This must exist, it won't be created)<br> TARGETSITE - The website where the virtual directory is to be created (NOTE: This is the <strong><em>metabase value</em></strong> for the web site... For example: "/LM/W3svc/2". Also note that the site must exist).</p> <p>There is a full list of properties for the installer can be found <a href="http://msdn.microsoft.com/en-us/library/aa370905.aspx" rel="noreferrer">here</a>.</p> <p>If you really want better control over the IIS setup I would suggest changing your project to a standard Windows Installer project and creating custom Install actions so that you can programatically create AppPools. A good place to start to understand programmaticly creating these things is <a href="http://msdn.microsoft.com/en-us/library/ms524896.aspx" rel="noreferrer">here</a>.</p> <p>The biggest reason for doing it this way is that custom actions run <strong><em>after</em></strong> prompting but the app pool and web sites must be created <strong><em>before</em></strong> the installer can prompt.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload