Automatic account creation is now enabled. Captcha authentication required for account creation and editing unless you are trusted here.

From WiX Wiki at MindCapers

Extension Schemas

Each WiX extension uses its own schema. The first thing you need to do to use any extension is include a reference to the schema within the WiX element. Here is an example:

 
<Wix xmlns="http://schemas.microsoft.com/wix/2006/wi"
     xmlns:iis="http://schemas.microsoft.com/wix/IIsExtension"
     xmlns:util="http://schemas.microsoft.com/wix/UtilExtension">
 

Extension File Extension Change coming February/March 2008

We will be doing a change that will probably affect most users of WiX v3, so I wanted to get this notice out in the community to notify people of the upcoming change. Within the next few weeks we will be changing the file extension of WiX extensions from .dll to .wixext. There are several reasons why we think this is an important thing to do, which I've blogged about. Please see this blog article for more information and how this change will affect you.

How Does this Affect You?

If you use any of the standard WiX custom action extensions, then you'll have to change your build scripts to reference the new names. If you use MSBuild or Votive, then you'll have to change any references you have in your .wixproj files (<WixExtension> elements). You can do this manually by hand-editing the .wixproj file or you can do this by removing the old references (right mouse click and select "Remove") and then re-adding them.

 
<ItemGroup>
 
    <WixExtension Include="$(ProgramFiles)\Windows Installer XML v3\bin\WixIIsExtension.wixext" />
 
</ItemGroup>
 

We will also try to put out a similar reference for NMake and NAnt when the feature gets checked in.

From message to wix-users@lists.sourceforge.net on 12-Feb-2008 from Justin Rockwood.

WixDifxAppExtension

WixIISExtension

> With the below code, I am trying to launch multiple commands, however > I don't want to leave CMD prompts open for the two web browser > sessions. Also, the final "success" message does not appear until the > final CMD prompt is closed. How can I make this better?

If you're using WiX v3, check out the ShellExec custom action; it handles launching URLs without resorting to cmd.exe.

WixIsolatedAppExtension

WixNetFxExtension

WixOfficeExtension

WixSqlExtension

In the latest version of WiX v2 and WiX v3, SQL String/Script processing takes place before RemoveFiles and after InstallFiles, so the files should be in place when your script executes. Other things may not be in place (for example, GAC'd files definitely won't) so beware.

WixVSExtension

Util Extension

Wix 3 has different schemas to use depending your need. XmlConfig needs util schema, which you have to include it by adding

 
   xmlns:util="http://schemas.microsoft.com/wix/UtilExtension"
 

to your Wix node inside each .wxs file that uses XmlConfig . Also you have to make a reference to WixUtilExtension. When you use XmlConfig, you must prefix it with the util namespace, i.e., <util:XmlConfig />, in order for WiX to recognize as part of the util schema.

How to use XmlFile