oseif.blogg.se - Adding custom actions to advanced installer

The custom action only runs on the first installation of the application.

The Installer executes the custom action only if the component that contains the HTML file is installed to run locally on the computer.

The Installer executes the custom action only if the full UI level is used to install an application.

The sample must meet the following specifications. This approach may be used to launch a help tutorial at the end of the first installation of an application. The Installer installs the component that contains the file, and then publishes a control event at the end of the installation to run a custom action that opens the file.

How To: Install DirectX 9.The following example illustrates how to launch an HTML file at the end of an installation.

How To: Get the parent directory of a file search.

How To: Reference another DirectorySearch element.

How To: NGen managed assemblies during installation.

How To: Create a shortcut to a web page.

How To: Create a shortcut on the Start Menu.

How To: Read a registry entry during installation.

How To: Write a registry entry during installation.

How To: Check the version number of a file during installation.

Building WiX Projects In Team Foundation Build.

Integrating WiX Projects Into Daily Builds.

Now as part of your installation, whatever "FooAction" is supposed to perform, you should see happen after the InstallFiles action. C:\test> candle product.wxs ca.wxsĬ:\test> light product.wixobj ca.wixobj –out product.msi Here are the compile, link, and installation steps.

Now that we have two files to link together our call to light.exe gets a little more complicated.

Those three lines are all you need to add to your Windows Installer package source file to call the "FooAction" CustomAction. We would need to link this source file along with a source file that contained or to successfully complete. Remember linking requires that you have an entry section. That little bit of code should compile but it will not link. We're done with editing the "ca.wxs" source file. Rather than put the CustomAction definition in the same source file as our product definition, let's exercise a little modularity and create a new source file to define the CustomActions called "ca.wxs". Before you start, you will need a sample dll that has an entrypoint called "FooEntryPoint". A common sample people use is a dll customaction that launches notepad.exe or some other application as part of their install. This example will show how to author a binary CustomAction called "FooAction". Now that you’re comfortable with the basics for creating Windows Installer packages, let’s take it to the next level and add a CustomAction. Previous page next page Adding Custom Actions