The Windows executables in this package are ready to be distributed. No special installation is required.

1.Make a copy of the 32- or 64-bit eViewer.exe and optionally rename the file.

2.Deploy the renamed file along with your software.

3.For localized distributions, supply a custom language file

4.For application online help use the URL-style command line syntax.

Don't register the .ewriter extension

We recommend that you don't register the .ewriter extension as part of your installation. Instead, always make your calls explicitly to your installed copy of the eViewer app and your own help files. This guarantees that you are using the same viewer that was up to date when you generated your help.

Consider using a different extension for your own help files

It is also a good idea to change the extension of your help files to your own version. If you do this, you can register your extension to your installed version of the eViewer application so that your users can open your help files themselves by double-clicking on them.

Then you don't get any conflicts if the user gets .ewriter files from somewhere else. If they open .ewriter files on Windows 10 and 11 they will get the Windows Store version of eViewer automatically (and that extension is required for the Store viewer), and that then doesn't create any conflicts: The .ewriter extension is always used for the Store version and your application always opens your help files with your installed version of the viewer.

The MacOS installation package is not ready to be distributed. You need to configure it for installation with your software first.

When you distribute a copy of the MacOS eViewer, you must change the custom URL scheme that the app registers. Custom URL schemes are global on MacOS and if multiple apps register the same URL scheme, there is no mechanism for the operating system to decide which app to call for this scheme.

Procedure:

1.Make a copy of eViewer.app and rename the file.

2.Change the URL schemes for the renamed viewer app:

a.Open the package content in Finder (CTRL+Click ➔ Show package content)

b.Inside the package, locate the /Contents folder and the file Info.plist
 

c.Open Info.plist with XCode

d.Navigate to URL Types ➔ Item 0 ➔ URL Schemes ➔ Item 0

e.Change the URL name from "ewriter" to your own unique identifier.
You must use this custom URL scheme in the URL-style command syntax.
For more information please refer to Defining a custom URL scheme on developer.apple.com.
 

 

f.Now this is a good opportunity to change the registered file extension as well, just in case you are using a different file extension than ".ewriter". Navigate to Document Types ➔ Item 0 ➔ Document Extensions ➔ Item 0 and enter your custom file extension:
 

 

3.Deploy the renamed app package along with your software.

4.For localized distributions, supply a custom language file

5.For application online help use the URL-style command line syntax.