From Crystal Reports for Visual Studio or an
older version of Crystal Reports Developer you can migrate upwards to Crystal Reports Developer.
The chart below shows migration issues that may
occur when you upgrade from an earlier version of Crystal Reports Developer to a more recent
version of Crystal Reports Developer.
It is not recommended to migrate from Crystal
Reports Developer to Crystal Reports for Visual Studio. For more information, see
Migration
from Crystal Reports Developer to Crystal Reports for Visual Studio Is Not Recommended.
For information on how to migrate from the RDC
version, see
Migration
from RDC (Crystal Reports for Visual Basic 6) to .NET.
For a diagram that demonstrates migration across
versions, see
Migration
diagram.
To determine which version of Crystal Reports
you are running, see
Crystal
Reports Versions.
| When migrating from a
previous version to the version below
| Is
migration automatic?
| Migration
approach
|
| Crystal Reports 9
| Yes
| Version 9 shipped with a migration utility, ProjectMigrator.exe, which migrates Visual
Studio .NET 2002 applications to Crystal Reports 9.
|
| Crystal Reports 9.2
| No
| Version 9.2 did not ship with a utility. Migration must be done manually. At the top of
each Web Form (in html view) and in the web.config file, the version number of each Crystal Reports
assembly must be manually updated.
|
| Crystal Reports 10
| Yes
| Crystal Reports 10 automatically upgrades your previous projects to the current version.
The ProjectMigrator.exe is no longer needed to migrate projects that were created with older
versions of Crystal Reports. If a project has references to older components, the user is prompted
to upgrade.
When you click the Yes button, the projects and its
files are upgraded to the current version of Crystal Reports. When you click the No button, the
project is adjusted to use the original references. Some of the earlier features become disabled,
because the older components do not have that particular functionality.
.gif)
Note
| | If the project file (any ASPX file that has any Crystal Reports
components or the web.config file) is locked, the upgrade or fix fails.
| |
| Crystal Reports 11
| Yes
| Crystal Reports 11 automatically upgrades your previous projects to the current version.
The ProjectMigrator.exe is no longer needed to migrate projects that were created with older
versions of Crystal Reports. If a project has references to older components, the user is prompted
to upgrade.
When you click the Yes button, the projects and its
files are upgraded to the current version of Crystal Reports. When you click the No button, the
project is adjusted to use the original references. Some of the earlier features become disabled,
because the older components do not have that particular functionality.
|
Note
| | If the project file (any ASPX file that has any Crystal Reports
components or the web.config file) is locked, the upgrade or fix fails.
| |
Ensure that Crystal Reports Developer upgrades
the version within Visual Studio
When you install Crystal Reports Developer,
Crystal Reports for Visual Studio is upgraded to Crystal Reports Developer.
This version includes the full version of the
embedded Crystal Reports Designer, an upgraded Business Objects Services node in the Server
Explorer, and the latest Crystal Reports SDK assemblies.
Some full versions of Crystal Reports ship
without developer tools and therefore do not upgrade the Crystal Reports for Visual Studio. If you
intend to upgrade to a full version of Crystal Reports within Microsoft Visual Studio, verify that
the version you are installing has the developer tools.
See Also