Products/ServicesDownloadsSupportPricingBuyContactAbout


F.A.Q.
Screenshots

VISE X
Installer VISE for Mac
Installer VISE for Windows
FileStorm
Installer Consulting Services

 

VISE X is quite simply the best software installer for the Mac OS X, period! With VISE X you can easily build a Universal (universal binary) installer that will reliably deliver your product to your customers. You can focus your energy on developing your software without worrying about the complicated details of writing an installer script.

VISE X builds upon the strengths of Installer VISE, but is a separate code base. The two products will be maintained and advanced separately. Separating the code base allowed us to focus VISE X functionality on Mac OS X.

Download VISE X for Mac OS X What's new in version 5.1?

How does VISE X compare to Installer VISE and FileStorm?
Check out our comparison chart .

 How to License VISE X

The following forms are in Adobe Acrobat format (pdf). If you do not already have it installed, please click the button to the right to get Adobe Acrobat Reader directly from Adobe. (Acrobat and the Acrobat logo are trademarks of Adobe Systems Incorporated.)

To license VISE X, download the VISE X License Agreement . This file contains instructions on licensing, as well as pricing information.

You can download the Order Form and fax it to us along with your completed license agreement.

As soon as we receive your completed license agreement we will contact you with your serial number so you can begin shipping your installers right away.

You can also download the Renewal/Cancellation Form

 VISE X Feature List:
·  Builds Universal (universal binary) installers for use on both Intel- and PowerPC-based Macs
·  VISE X installers display a standard Mac OS X user interface, including Aqua fonts and controls, Mac OS X property sheets and Installer background images with transparency
·  Support for custom external code (as CFPlugins) ·  Work with installer projects as XML
·  Installer builds as an application bundle ·  Automatically create updaters for application bundles
·  Support for Mac OS X v10.9. Mavericks ·  Support for Mac OS X text and graphic file formats
·  Custom form editor optimized for Mac OS X ·  Destination and install locations optimized for Mac OS X
·  Zip post processing ·  Mac OS X disk image build target
·  Improved support for long filenames ·  Improved support for Mac OS X localization
·  Increased length of variables values to 255 ·  Increased filename limit from 63 to 255 characters
·  Search filters in the Bring Up To Date window ·  Ability to set a background graphic for the installer
·  Display QuickTime movies in splash screens and billboards ·  XML translator option for localization

 What's New in version 5.1

This update is free to users with current VISE X licenses. Your existing serial number will register the new version.

VISE X 5.1 RELEASE NOTES

VISE X 5.1 is our update for compatibility with Mountain Lion and its new security feature, Gatekeeper, which depends on code signing to control whether apps can be installed. In addition to signing VISE X so that it will continue to work on Mountain Lion, we added features that will make it convenient for developers to code sign and verify their apps and installers.

Mountain Lion Compatibility

We have tested this version of VISE X and verified its compatibility with Apple’s Mac OS X v10.8 Mountain Lion.

Along with the compatibility testing, Gestalts in VISE X have been updated for Mountain Lion. You can use the new "MacOS X 10.8 or Greater" Gestalt to ensure that install actions take place only on the proper Mac OS versions.

There was no need to create additional search/install locations for Lion. 

Code Signing and Code Verification

To be able to run on Mountain Lion under Gatekeeper’s default security option, apps must be code signed. Developers can get a unique Developer ID from Apple, and use that ID to code sign their apps.

VISE X 5.1 provides the following new features to make code signing convenient for developers:

  • A "CodeSign Bundle" option in the Extras menu uses the developer’s unique Developer ID to code sign the specified app.
  • A "Check CodeSign Status" option in the Extras menu verifies code signing for the specified app.
  • A "Code Sign Bundle" Post Processing option for build targets automatically signs installers once they are built.

Note: The following instructions require developers to have already imported their Developer IDs into Keychain Access.

Code signing bundles

Developers have several options for signing their code, including automatic signing with Xcode, and manual signing with the codesign(1) command. For added convenience, VISE X provides another option, which is available as "CodeSign Bundle" in the Extras menu.

When you select "CodeSign Bundle", there will be a prompt to choose a bundle to sign. VISE X will then look in your keychain, and sign the specified bundle using the first certificate that begins with "Developer ID".

You can verify your code signing by selecting "Check CodeSign Status" from the Extras menu, and then choosing a bundle to check.

Code signing installers

Because your installers also need to be signed, VISE X provides the ability to automatically sign bundle installers as part of post processing. To enable this feature, go to the desired build target’s Post Processing tab and select the "Code Sign Bundle" check box. Next, enter the code sign identity that you want to use for signing installers for this target. You typically would enter only the portion of the certificate name following the colon. For example, if the complete certificate name is "Developer ID Application: XY Builders, Inc." it would be enough to enter "XY Builders, Inc." in the build target.

More detailed information on code signing is available at the Apple Developer site.

Bug Fixes

  • On Mountain Lion, authenticated installers using localization were unable to detect the machine’s default language when they were relaunched. In these instances, the installers were incorrectly defaulting to English. 
  • When setting options in a single Get Info window for multiple items that have been selected in the VCT, the “Set Owner To Root” option could be toggled inadvertently.
  • VISE X would sometimes crash when building installers. This issue was present on both Intel and PPC processors, and could be triggered by using a billboard, or having certain Gestalt flags or Package flags set.
  • On Mac OS X v10.7 Lion, installers were able to add items to the Dock, but they were not able to remove the items on an uninstall.

Other Changes

  • We removed "Undo Mach-O Prebindings" and "Redo Mach-O Prebindings" from the Extras menu. Prebinding is unnecessary in OS X v 10.3.4 and later versions.

Known Issues

  • When authenticated installers are running on Mac OS X v10.6, the OS requires users to authenticate a second time under certain scenarios. The second authentication is required when an item is set to “Ask User” for the install location, and when the user saves or prints license agreements or Read Me files.
  • Standalone uninstallers are placed on the root of the install destination. To allow that installation to work on Mac OS X v10.7 or later, the installers must be set up to require OS X authentication. For information on a workaround that does not require authentication, please contact MindVision support.
  • If you use the Post Processing section of build targets to create a Tarball (.tar.gz) version of your installer, you should restrict the Tarball file name to 29 characters or less for compatibility with Mac OS X versions prior to 10.4. Otherwise, if you make the Tarball name longer than 29 characters, the uncompressed installer will not launch on the earlier OS versions. (If you are confident that the installer will be used on Mac OS X versions 10.4 or greater, you can use up to 31 characters for the Tarball file name.)
  • VISE X supports installing to iDisk volumes on Mac OS X versions 10.4 or greater only. On earlier OS versions, the installers’ Select Destinations dialog will not show iDisk volumes (in most instances).
  • When creating Read Me and License Agreement files with embedded graphics, you should not use Microsoft Word RTF format. The reason is that there are compatibility issues with displaying these files from VISE X installers.
  • VISE X uses UTF-8 encoding to allow installers to display text in double-byte character set languages. You must use the translator XML file to enter the UTF-8 characters.
  • Due to Apple's deprecation of Open Transport, we are no longer able to support web based installer functionalilty.

Download VISE X for Mac OS X

 
Copyright 1997-2006 MindVision Software
DMCA and Corporate Policies | Security/Privacy | Copyright 2014, Digital River, Inc.