Upgrade versus Update
An upgrade refers to a change in the major version of E-Prime, for example upgrading from E-Prime 2 to E-Prime 3. An update refers to a change in a minor version of E-Prime within the same major version, for example updating from E-Prime 3.0.3.60 to 3.0.3.80. The E-Prime experiment and the E-Prime software can be upgraded or updated.
Upgrading Experiments (experiment specification files)
Experiments that were created in E-Prime 1.2 and 2.x can be upgraded into E-Prime 3.0 and typically require little to no modification. However, while experiments that are created in E-Prime 3.0 will apply any new default values (see RELEASE INFO: E-Prime 2.0 to E-Prime 3.0 Changes [27092]) and have access to new features, experiments that were written in earlier versions of E-Prime and are upgraded will not use any new default values and will not have new features incorporated into them. This enables the upgraded E-Prime 3.0 version of the experiment to perform as similar to the original version as possible. Once the need to maintain functional consistency with earlier version ends, primarily when a continuing study is completed, then an experiment author can take advantage of E-Prime 3.0's new features in an upgraded experiment by creating new objects that use the new default values and selecting various features on the relevant objects, such as the Buttons that were introduced with E-Prime 3.
Any experiment created in E-Prime 1.x or E-Prime 2 and opened in the latest version of E-Prime generates a prompt to either upgrade the experiment to E-Prime 3.0 (i.e., save the experiment as an .es3 file) or exit the E-Studio application.
Upgrading E-Prime software
Researchers who are currently running E-Prime 1.x or E-Prime 2 can upgrade to E-Prime 3. Since experiments that were created in earlier versions or E-Prime (e.g., .es1 or .es2 files) can be upgraded to E-Prime 3 (saved as es3 files), researchers do not have to re-implement previously created experiments when they upgrade to E-Prime 3. Please contact sales@pstnet.com for information on upgrading your E-Prime software.
Updating E-Prime
Users who have created a PST Support Account and registered an E-Prime serial number can download any supported minor version of the software (see INFO: How to Register for Support and Access Downloads [27523]). Therefore, users can download and then install new minor versions of E-Prime when they are released or when they have completed a study (see RELEASE INFO: Using the latest version of E-Prime [30812]). E-Prime can check for updated versions. When a new version of E-Prime is detected, the E-Prime Check for Updates displays a prompt when the E-Studio application is launched that an update is available that may be downloaded from the Support site. Please view the following article for detailed information on E-Prime Check for Updates:
- INSTALL: Information sent when E-Prime Check for Updates queries for new versions of E-Prime [17835]
Protection for Incompatible E-Prime Extensions
E-Prime monitors the compatibility of E-Prime and any installed E-Prime Extensions for [Product]and therefore protects extensions that are too old or new for the currently installed E-Prime software. If E-Prime is updated to a version that is not compatible with an already-installed extensions, then E-Prime will detect and then block any Toolbox or runtime objects to be loaded when its version does not match that of the currently installed runtime. Check the Output window for warning messages in these circumstances.
Protection for Incompatible E-Run versions
The E-Run application can often run experiments that were compiled in a different minor version. For example, an ebs3 file that was generated from E-Prime 3.0.10.60 can be run by E-Run version 3.0.10.80. However, all major versions of E-Run (e.g. all versions of E-Run 3.0) are not compatible with all minor versions of the ebs file. See RELEASE INFO: E-Run Resolver dialog allows choosing runtime when no direct match is available [19362] for more information.
Previous Article: LICENSE: Registration and Validation [39159]
Comments
0 comments
Please sign in to leave a comment.