Showing results for 
Search instead for 
Did you mean: 

Upgrade Crystal reports 11 to the current version

0 Kudos

Our legacy crystal reports are developed on Crystal report 11 and are running in server on Crystal Reports Basic Runtime for Visual Studio 2008 (x64) version We are upgrading the reports using Crystal Report 2016 and use latest SDK to run them on Server. And these reports are called from ASP.Net project.

Can we use MVC to upgrade this ASP.Net project? Or should we use ASP page?

Please share some upgrade recommendations.

Thank You


Accepted Solutions (1)

Accepted Solutions (1)

Active Contributor
0 Kudos

I believe you can use either. However, you cannot use .NET Core, you have to use a Windows version of .NET because the SDK still has some COM objects in its internals which won't work on non-Windows OSs.

Also, your reports should work as-is if you're using ODBC. You'll just need to create ODBC connections with the same names as the old ones but using new database drivers. For other types of connections, you will probably need to update the connections in the reports to use the newer database client - there's a good chance the old one won't work.


0 Kudos

But MVC library doesn't provide CrystalReportViewer, right?. How can we render the reports on web application when using MVC?

Please share some recommendations on upgrading the project that is using CrystalReportViewer in MVC.

Answers (2)

Answers (2)

0 Kudos

Stand alone CR Designer and the Embedded Report Designer in Visual Studio and exporting to RPT format is the only way to update the version of the report.

You can get a list of the Report saved versions using this, puts it into a list box:

for (int x = 0; x < rpt.HistoryInfos.Count; x++)
    cbLastSaveHistory.Items.Add(rpt.HistoryInfos[x].BuildVersion.ToString() + ": Date: " + rpt.HistoryInfos[x].SavedDate.ToString());

cbLastSaveHistory.SelectedIndex = 0;
0 Kudos

As Dell indicated, Core is not supported due to the nature of the CR COM components.

There are no plans to support CORE, it would require a complete rewrite of our Assemblies and dll's.

Bottom line is you need to use ASP.NET and the full Framework 4.x and above.


0 Kudos

I was not talking about Asp.Net Core but just Asp.Net MVC.