strangekerop.blogg.se - View document properties word desktop app

View document properties word desktop app windows#

The name that appears in the File Explorer context menu. For more information about using this extension, see Integrate a packaged desktop app with File Explorer. This extension enables you to add options to the context menu that displays when users right-click a file in File Explorer.These options give users other ways to interact with your file such as print, edit, or preview the file. The file extension supported by your app.Īdd options to the context menus of files that have a certain file type If a user right-clicks a file in File Explorer and then selects the Open with option, your application appears in the list of suggestions. You can associate your packaged application with file type extensions.

The programmatic identifier (ProgID) that describes the application, component, and version of the desktop application from which you want to inherit file associations.Īssociate your packaged application with a set of file types The name must be all lower case characters with no spaces. You can use this name to organize and group file types. To do that, you'll specify the programmatic identifier (ProgID) of each application from which you want to inherit file associations. You can make sure that users open your new packaged application by default for specific types of files instead of opening the desktop version of your app. Make your packaged application open files instead of your desktop app WPF picture viewer with transition/migration/uninstallation lnk files that start the desktop version of your app. The Application User Model ID of your packaged app. Elements and attributes of this extension įind the complete schema reference here. You can point those shortcuts to your new packaged app. Your users might have pinned your desktop application to the taskbar or the Start menu. Point existing Start tiles and taskbar buttons to your packaged app It must always end with the ".exe" extension. The relative path to the executable to start when the alias is invoked.

The user can disable the AppExecutionAlias entry for your MSIX-packaged app in the App execution aliases page in Settings.Įlements and attributes of this extension.

They can uninstall the MSIX-packaged version of your app.

Users can turn off the redirection and launch your unpackaged app executable via these options: In your package manifest, add an AppExecutionAlias extension that registers the name of your unpackaged desktop app executable. Register your packaged app to be launched

If the special value * is used, the system will redirect to an AppExecutionAlias from any package.įor example: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\contosoapp.exeĪppExecutionAliasRedirectPackages = "Microsoft.WindowsNotepad_8weky8webbe" Packages are listed by their package family name, separated by semicolons.

AppExecutionAliasRedirectPackages (REG_SZ): The system will redirect only to the listed packages.

If the AppExecutionAlias extension is enabled, the packaged app will be activated using that value.

AppExecutionAliasRedirect (DWORD): If set to 1, the system will check for an AppExecutionAlias package extension with the same name as the executable.

Under this subkey, add the following values:.

In the registry, create a subkey with the name of your desktop app executable file under the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options key.

Register your packaged app to be launched when your unpackaged desktop app executable is launched.Īdd registry entries to redirect your unpackaged desktop app executable.

Add registry entries to redirect your unpackaged desktop app executable to your packaged app.

View document properties word desktop app windows#

This feature is supported in Windows Insider Preview Build 21313 and later versions.