File type and protocol associations model

Platforms

Clients - Windows 8

Servers - Windows Server 2012

Description

The file type and protocol association model has changed in Windows 8. Apps are no longer able to programmatically set themselves as the default handler for a file type or protocol. Instead, now the user always controls what the default handler is for a file type or protocol.

Manifestation

How this change presents to the user depends upon how the app is designed, for example:

• Many apps check to see if they are the default every time they run and, if they are not, they prompt the user to set them as default. However, because apps can no longer accurately query to determine which app is the default handler for a file type or protocol, neither of these operations works.
• Many apps have a dialog box or menu built in or in their installer that specifies the file types for which the app should serve as the default. However, because apps can no longer programmatically set themselves as the default handler for a file type or protocol, this no longer works.

Mitigation

There are several things users can do to accommodate these changes:

• Users are prompted contextually to choose a default app to handle file types, protocols, or both when one has not been specified
• Users are offered the option to change their default handler after installing new apps that can handle a file type or protocol
• The default programs control panel allows users to set defaults for an app, or for a file type, protocol, or both; apps can link to the control panel
• Defaults can be changed from Windows Explorer

Solution

As a result of these changes, this API guidance is provided:

• The functionality of some method calls within the IApplicationAssociationRegistration API has changed, and should no longer be used.
  • Do not call QueryAppIsDefault/QueryAppIsDefaultAll to determine if an app is the default
  • Do not call QueryCurrentDefault to determine which app (if any) is the current default
  • Do not call SetAppIsDefault/SetAppIsDefaultAll to set the default app
• The guidance going forward is:
  • Do not query to see which app is the default handler for file types or protocols
  • Do not attempt to monitor changes in the default handler for file types or protocols
  • Do not attempt to set an app as the default handler for file types or protocols
  • Do not attempt to manage defaults for file types or protocols from within an app
  • Do integrate with the Set Default Programs control panel if you want to allow users of your app to access the default management UI (the management UI within the app is no longer supported)
    • Calling IApplicationAssociationRegistrationUI::LaunchAdvancedAssociationUI allows the user to access the ‘Set Default Programs’ control panel page for the specified app

Tests

• Test to verify that apps register properly in Set Default Programs control panel
• Test to verify that apps register properly to appear in the OpenWith list for the file types, protocols, or both, that they register to handle
• Test to verify that new app notifications appear after your app is installed and the user invokes a file type, protocol, or both, that your app has registered to handle

Resources

• Best Practices for File Type and Protocol Associations in Windows Developer Preview Desktop Apps
• File Type Associations and AutoPlay Build Conference Presentation

Build date: 11/28/2012