VISE X helps users create installation programs for the distribution of software. You can package many files together into one installer, and easily distrubute your software package to others. You can customize the installer to place files in specified areas of their computer, run AppleScripts during installation, allow multiple language installs, and build CD-ROM installers quickly.
What's new in VISE X
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.
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.
On OS X 10.8 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 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.
On OS X 10.8 Mountain Lion, installers were unable to correctly add items to the Dock (there were unneeded second entries). Also, installers could not remove items from the Dock on an uninstall.
VISE X now requires a save when closing a VCT after "crunching" it. This change ensures that renumbering is saved, so the prompt to crunch the VCT doesn't reappear the next time the VCT is opened.
Web installers built on Intel processers would sometimes report errors.
On OS X 10.8 Mountain Lion when using authentication, sub-launching installers
did not always work correctly.
Authenticated installers would fail to display double-byte languages correctly under OS X 10.8 Mountain Lion.
When importing XML to create a new VCT, the settings controlling when to call external code (such as before the install) were lost.
The restart warning message for installers was too small to accommodate Dutch and Portuguese translations.
Bundle updaters would remove folders that appeared to be empty, but in actuality contained zero K delete actions.
We removed "Undo Mach-O Prebindings" and "Redo Mach-O Prebindings" from the Extras menu. Prebinding is unnecessary in OS X 10.3.4 and later versions.
When authenticated installers are running on OS X v0.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 OS X 10.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 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 OS X versions 10.4 or later 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.