|
| |
Visual Prolog 7.0 Upgrade Notes
See also
Upgrade Discounts and Prices
- Owners of Visual Prolog 7.0 can upgrade freely to the latest build
of version 7.0.
- Owners of Visual Prolog 6.3 can upgrade to Visual Prolog 7.0 for
$149.
- Otherwise the price is $299.
To check whether your are eligible for upgrade discounts and to order
the latest public build of Visual Prolog
7.0 Commercial Edition with an appropriate
discount, please, use the menu item from your Visual Prolog Integrated Development
Environment (IDE).
Upgrading Projects from Visual Prolog
7.0 Builds 7001, 7002, and 7003 to the Build 7004
- Visual Prolog 7.0, Build 7004 is available as an installation program that might be used
for a complete replacement of the builds
7001, 7002,
7003.
The new version will be installed by default to C:\Program
Files\Visual Prolog 7.0.
- To make bug fixes and improvements in the Build 7004 available, it is
recommended to rebuild your projects created by the previous builds of Visual
Prolog 7.0.
- Visual Prolog 7.0 examples included into the distribution have not been
changed, except the ISAPI example provided with the Commercial Edition in the
Build 7003, so you
do not need to reinstall other examples if they are installed at your
computer.
However if you decide to install the examples once more, note that they will
be installed into the same default examples folder. If you want to preserve
your updates to the examples, please, install the examples included into the
Build 7003 into a different folder.
- Beginning with the Build 7003, the Commercial Edition of Visual Prolog 7.0 includes an updated
version of the Help generation Tool (PRODOC) that requires Microsoft .NET
Framework 2.0 to be installed at a computer.
If you have installed Visual
Prolog at a computer, where Microsoft .NET Framework 2.0 is missed, and want
to use PRODOC, you need to do the following:
-
Install Microsoft .NET Framework 2.0.
-
Run MILHTMLParserRegister.exe
from the bin directory.
You may ignore this requiring if you do no need PRODOC.
Upgrading Projects from Visual Prolog 6.3 to
Visual Prolog 7.0
- By default, Visual Prolog 7.0 will not replace a previous version of Visual Prolog while
installation. The new version will be installed by default to C:\Program
Files\Visual Prolog 7.0.
- Visual Prolog 7.0 projects are not fully backward-compatible.
Visual Prolog 6.3 and earlier IDE will not allow opening projects modified by Visual Prolog
7.0 IDE.
It is recommended to create a backup copy of your project before opening
it by the Visual Prolog 7.0 IDE.
- If you are going to use Visual Prolog 7.0 and Visual Prolog 6.x
simultaneously at the same computer, it is recommended to switch the IDE
setting "Open Project at Startup" OFF, because the IDE in the both
versions use the same registry entries for the list of opened projects.
Avoid opening projects by double-clicking on prj6 files
if you have different versions of Visual prolog installed at one computer.
- Some changes
require automatic updates in Visual Prolog7.0 projects.
Therefore, it is recommended to make the project file (PRJ6) writable before
the first build.
- After you open your project in Visual prolog 7.0 IDE, the IDE will fulfill necessary updates in the project
structure.
After this, rebuild the project with the help of the
and answer "Yes to All" to the message "The new
module is required to be added into the project".
- Note that language updates in Visual prolog 7.0 may cause some compiler errors
in you project:
- The following new keywords have been introduced:
if
then
else
foreach
do
That means that they can no longer be used as identifiers (Visual Prolog
version 6.2 and 6.3 gave a warning about this).
- Stronger treatment of types might require some changes in your program.
Typically change of declarations or insertions of explicit conversions might be
necessary.
- Reference domains are not supported anymore. If your project uses
reference domains, we recommend to read the "How To Erase Reference Domains from a Project"
tutorial.
- G-stack is not used in Visual Prolog 7.0 anymore. Hence, all G-stack
related predicates have been removed.
- Beginning with Visual Prolog 7.0 some accelerator keys have been
changed to comply with Microsoft standards.
New accelerator
key bindings are described in Help. You are welcome to print out the
New Visual Prolog 7.0 IDE Accelerator Keys
table. from this site.
- Beginning with Visual Prolog 7.0 exception package has been changed:
- TraceId is not more a number; it is a
pointer to the object, which stores the information about an exception.
- PFC does not store facts about exceptions anymore; this gives
an essential
improvement in the performance of your programs.
- The continued part of continued exceptions should be handled in
a
new way. The Exceptions Handling
tutorial explains how to do it. However, if you use
exceptiondump class,
you, of course, can see everything.
- The positions in exception dump are much more informative,
since you can
see the entire stack of positions.
- Prolog Development Center always suggests the latest build of Visual
Prolog 7.0 as a shipping release.
Please see Upgrading Projects from Visual Prolog 7.0
Builds 7001, 7002, and 7003 to the Build 7004.
Upgrading Projects from Visual Prolog 6.1 and
Visual Prolog 6.2 to Visual Prolog 7.0
- Please see Upgrading
Projects from Visual Prolog 6.3 to Visual Prolog 7.0
- Upgrading Projects from Visual Prolog 6.x versions earlier than Visual Prolog
6.3 to Visual Prolog 7.0 may require additional updates. See:
Upgrading Projects from Visual Prolog 5.x
Prolog Development Center provides the
Migration Tool that will assist you
to migrate your Visual Prolog 5.x projects.
You are welcome to download the Migration
Tool for free with the help of the menu item in the IDE.
| |
|
