-->

Preview App For Windows
Preview For Mac
Preview Mac App To Windows 7

Installing QuickLook, the app has no interface to speak of. It works primarily as an extension to File Explorer. If you select a file and press spacebar, you can see a quick preview of what the file is, with the option of opening it in an actionable app. For example, previewing a PDF file will give you the option of opening Microsoft Edge as well.
Kindle Previewer 3 can be used on machines running Mac OS X v10.11 or later and Microsoft Windows 8.1 (64-bit) or later. For both Mac and Windows PC, we recommend that the computer you use to run the Kindle Previewer meets or exceeds the following requirements:. Processor: 1.2 GHz or faster. RAM: Minimum 4 GB, 8 GB recommended.

Note

In the Preview app on your Mac, choose View Thumbnails. Drag the files to the window’s sidebar. See also Convert graphics file types in Preview on Mac Print PDFs and images in Preview on Mac Resize, rotate, or flip an image in Preview on Mac.

The Desktop App Converter tool is deprecated. We recommend that you use the MSIX Packaging Tool instead.

The Desktop App Converter (DAC) creates packages for desktop applications to integrate with the latest Windows features, including distribution and servicing via the Microsoft Store. This includes Win32 apps and apps that you've created by using .NET 4.6.1.

While the term 'Converter' appears in the name of this tool, it doesn't actually convert your app. Your application remains unchanged. However, this tool generates a Windows app package with a package identity and the ability to call a vast range of WinRT APIs.

You can install that package by using the Add-AppxPackage PowerShell cmdlet on your development machine.

The converter runs the desktop installer in an isolated Windows environment by using a clean base image provided as part of the converter download. It captures any registry and file system I/O made by the desktop installer and packages it as part of the output.

Important

Desktop App Converter is supported on Windows 10, version 1607, and later. It can only be used in projects that target Windows 10 Anniversary Update (10.0; Build 14393) or a later release in Visual Studio.

The DAC does more than just generate a package for you

Here's a few extra things it can do for you.

Windows 10 Creators Update

✔️ Automatically register your preview handlers, thumbnail handlers, property handlers, firewall rules, URL flags.

✔️ Automatically register file type mappings that enable users to group files by using the Kind column in File Explorer.

✔️ Register your public COM servers.

Windows 10 Anniversary Update or later

✔️ Automatically sign your package so that you can test your app.

✔️ Validate your application against packaged app and Microsoft Store requirements.

To find a complete list of options, see the Parameters section of this guide.

If you're ready to create your package, let's start.

First, prepare your application

Review this guide before you begin creating a package for your application: Prepare to package a desktop application. Mac mail app not searching.

Make sure that your system can run the converter

Make sure that your system meets the following requirements:

Windows 10 Anniversary Update (10.0.14393.0 and later) Pro or Enterprise edition.
64 bit (x64) processor
Hardware-assisted virtualization
Second Level Address Translation (SLAT)
Windows Software Development Kit (SDK) for Windows 10.

Start the Desktop App Converter

Download and install the Desktop App Converter.
Run the Desktop App Converter as an administrator.
A console window appears. You'll use that console window to run commands.

Set a few things up (apps with installers only)

You can skip ahead to the next section if your application doesn't have an installer.

Identify the version number of your operating system.
To do that, type winver in the Run dialog box, and then choose the OK button.
You'll find the version of your Windows build in the About Windows dialog box.
Download the appropriate Desktop app Converter base image.
Make sure that the version number that appears in the name of the file matches the version number of your Windows build.
Important
If you're using build number 15063, and the minor version of that build is equal to or greater than .483 (For example: 15063.540), make sure to download the BaseImage-15063-UPDATE.wim file. If the minor version of that build is less than .483, download the BaseImage-15063.wim file. If you've already setup an incompatible version of this base file, you can fix it. This blog post explains how to do that.
Place the downloaded file anywhere on your computer where you'll be able to find it later. Best engineering software.
In the console window that appeared when you started the Desktop App Converter, run this command: Set-ExecutionPolicy bypass.
Set up the converter by running this command: DesktopAppConverter.exe -Setup -BaseImage .BaseImage-1XXXX.wim -Verbose.
Restart your computer if you're prompted to do so.
Status messages appear in the console window as the converter expands the base image. If you don't see any status messages, press any key. This can cause the contents of the console window to refresh.
When the base image is fully expanded, move to the next section.

Package an app

To Package your app, run the DesktopAppConverter.exe command in the console window that opened when you started the Desktop App Converter.

You'll specify the package name, publisher and version number of the application by using parameters.

Note

If you've reserved your app name in the Microsoft Store, you can obtain the package and publisher names by using Partner Center. If you plan to sideload your app onto other systems, you can provide your own names for these as long as the publisher name that you choose matches the name on the certificate you use to sign your app.

A quick look at command parameters

Here are the required parameters.

You can read about each one here.

Examples

Here's a few common ways to package your app.

Package an application that has an installer (.msi) file

Point to the installer file by using the Installer parameter.

Preview App For Windows

Important

There are two important things to keep in mind here. First, make sure that your installer is located in an independent folder and that only files related to that installer are in the same folder. The converter copies all of the contents of that folder to the isolated Windows environment.
Secondly, if Partner Center assigns an identity to your package that begins with a number, make sure that you also pass in the -AppId parameter, and use only the string suffix (after the period separator) as the value of that parameter.

If your installer includes installers for dependent libraries or frameworks, you might have to organize things a bit a differently. See Chaining multiple installers with the Desktop Bridge.

Package an application that has a setup executable file

Point to the setup executable by using the Installer parameter.

Important

If Partner Center assigns an identity to your package that begins with a number, make sure that you also pass in the -AppId parameter, and use only the string suffix (after the period separator) as the value of that parameter.

The InstallerArguments parameter is an optional parameter. However, because the Desktop App Converter needs your installer to run in unattended mode, you might have to use it if your application needs silent flags to run silently. The /S flag is a very common silent flag, but the flag that you use might be different depending on which installer technology you used to create the setup

Preview Mac App To Windows