How to register file types/extensions with a WiX installer?

by

Unfortunately there’s no way to do a “safe” association with Windows Installer.

We just write everything out to the registry and then have a separate component that takes over the system-wide default and is only installed if no other application has already registered itself as the default.

With Vista there’s the new “default programs” interface, again you write everything out to the registry. Here’s a complete example that we’re using in our installer. (WiX 3.0)

Update: 12 months have passed since my original answer and I have a better understanding of file associations. Rather than writing everything manually I’m now using proper ProgId definitions which improves handling for advertised packages. See the updated code posted in response to this question. 

<Component ....>
    <RegistryValue Root="HKLM" Key="SOFTWARE\AcmeFoobar\Capabilities" Name="ApplicationDescription" Value="ACME Foobar XYZ Editor" Type="string" />
    <RegistryValue Root="HKLM" Key="SOFTWARE\AcmeFoobar\Capabilities" Name="ApplicationIcon" Value="[APPLICATIONFOLDER]AcmeFoobar.exe,0" Type="string" />
    <RegistryValue Root="HKLM" Key="SOFTWARE\AcmeFoobar\Capabilities" Name="ApplicationName" Value="ACME Foobar" Type="string" />
    <RegistryValue Root="HKLM" Key="SOFTWARE\AcmeFoobar\Capabilities\DefaultIcon" Value="[APPLICATIONFOLDER]AcmeFoobar.exe,1" Type="string" />
    <RegistryValue Root="HKLM" Key="SOFTWARE\AcmeFoobar\Capabilities\FileAssociations" Name=".xyz" Value="AcmeFoobar.Document" Type="string" />
    <RegistryValue Root="HKLM" Key="SOFTWARE\AcmeFoobar\Capabilities\MIMEAssociations" Name="application/xyz" Value="AcmeFoobar.Document" Type="string" />
    <RegistryValue Root="HKLM" Key="SOFTWARE\AcmeFoobar\Capabilities\shell\Open\command" Value="&quot;[APPLICATIONFOLDER]AcmeFoobar.exe&quot; &quot;%1&quot;" Type="string" />

    <RegistryValue Root="HKLM" Key="SOFTWARE\RegisteredApplications" Name="Acme Foobar" Value="SOFTWARE\AcmeFoobar\Capabilities" Type="string" />

    <RegistryValue Root="HKLM" Key="SOFTWARE\Classes\.xyz" Name="Content Type" Value="application/xyz" Type="string" />
    <RegistryValue Root="HKLM" Key="SOFTWARE\Classes\.xyz\AcmeFoobar.Document\ShellNew" Value="" Type="string" />
    <RegistryValue Root="HKLM" Key="SOFTWARE\Classes\.xyz\OpenWithList\AcmeFoobar.exe" Value="" Type="string" />
    <RegistryValue Root="HKLM" Key="SOFTWARE\Classes\.xyz\OpenWithProgids" Name="AcmeFoobar.Document" Value="" Type="string" />
    <RegistryValue Root="HKLM" Key="SOFTWARE\Classes\Applications\AcmeFoobar.exe\SupportedTypes" Name=".xyz" Value="" Type="string" />
    <RegistryValue Root="HKLM" Key="SOFTWARE\Classes\Applications\AcmeFoobar.exe\shell\open" Name="FriendlyAppName" Value="ACME Foobar" Type="string" />

    <RegistryValue Root="HKLM" Key="SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\AcmeFoobar.exe" Value="[!AcmeFoobar.exe]" Type="string" />
    <RegistryValue Root="HKLM" Key="SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\AcmeFoobar.exe" Name="Path" Value="[APPLICATIONFOLDER]" Type="string" />

    <RegistryValue Root="HKLM" Key="SOFTWARE\Classes\SystemFileAssociations\.xyz\shell\edit.AcmeFoobar.exe" Value="Edit with ACME Foobar" Type="string" />
    <RegistryValue Root="HKLM" Key="SOFTWARE\Classes\SystemFileAssociations\.xyz\shell\edit.AcmeFoobar.exe\command" Value="&quot;[APPLICATIONFOLDER]AcmeFoobar.exe&quot; &quot;%1&quot;" Type="string" />

</Component>



<Component ....>
    <ProgId Id="AcmeFoobar.Document" Description="ACME XYZ Document">
        <Extension Id="pdf" ContentType="application/xyz">
            <Verb Id="open" Command="Open" TargetFile="[APPLICATIONFOLDER]AcmeFoobar.exe" Argument="%1" />
        </Extension>
    </ProgId>

    <Condition><![CDATA[DEFAULTVIEWER=1]]></Condition>
</Component>

More Related Contents:

  1. Change my component GUID in wix?
  2. Extract MSI from EXE
  3. How to implement WiX installer upgrade?
  4. Why does MSI require the original .msi file to proceed with an uninstall?
  5. What is the wix ‘KeyPath’ attribute?
  6. Why use Windows Installer XML (WiX) over VDPROJ?
  7. How to associate application with existing file types using WiX installer?
  8. MSI Reference Counting: Two products install the same MSIs
  9. How do I fix the upgrade logic of a wix setup after changing InstallScope to “perMachine”
  10. Wix custom uninstallation action – how to run before msi removing files
  11. How to make better use of MSI files
  12. What installation product to use? InstallShield, WiX, Wise, Advanced Installer, etc [closed]
  13. Changing text color to Wix dialogs
  14. Removing files when uninstalling WiX
  15. Adding Custom prerequsites to visual studio setup project
  16. Silent installation of a MSI package
  17. Uninstall from Control Panel is different from Remove from .msi
  18. What is the benefit and real purpose of program installation?
  19. Does an universal cross-platform installer exists? [closed]
  20. How to Explicitly Remove dll During Majorupgrade Using Wix Toolset
  21. Create MSI from extracted setup files
  22. In WiX files, what does Name=”SourceDir” refer to?
  23. How to include wxi file into wxs?
  24. wix installer ice03 Invalid Language Id
  25. Odd ‘Program name’ when installing signed msi installer [duplicate]
  26. How to build a minimal WiX installer UI without a license page?
  27. WIX Installer: Prevent installation on Windows Server 2012 R2
  28. How to deny folder permission to Users with wix installer
  29. Speed up Build-Process of WiX-Installer
  30. WiX – Doing a major upgrade on a multi instance install

Leave a Comment