Migration Issues for Crystal Reports for Visual Studio
From Crystal Reports for Visual Studio you can migrate upwards to newer versions, either to a more recent version of Crystal Reports for Visual Studio or to Crystal Reports Developer.
Note
For more information on Crystal Reports for Visual Studio, see What is Crystal Reports for Visual Studio?.
The chart below shows migration issues that may occur when you upgrade from an earlier version of Crystal Reports for Visual Studio to a later version.
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 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 for Visual Studio .NET 2002
|
Not applicable
|
This is the original version; therefore, no migration is necessary.
|
Crystal Reports for Visual Studio .NET 2003
|
Windows - Partial Web - No |
Automatic migration of Windows projects to Visual Studio .NET 2003 is not explicitly provided. However, in most cases the migration of Windows projects is nearly automatic, because the majority of assembly references are resolved to the new assembly version upon opening of the project. For Web applications, 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 for Visual Studio 2005
|
Yes
|
|
Crystal Reports Basic for Visual Studio 2008
|
Yes
|