Crystal Reports, Developer for Visual Studio Downloads

Version of Visual Studio

Compatible Crystal Reports for Visual Studio Support Pack

VS 2010

All support packs

VS 2012

SP 7 and higher

VS 2013

SP 9 and higher

VS 2015C

SP14

VS 2015

SP15 and higher

VS 2017

SP21 and higher

VS 2019

SP25 and higher (note: some issues reported with embedded Report Designer)

VS 2019

SP 26 and higher (note: above issues resolved)

VS 2022

SP32 and higher (note: option of 64 bit installer for VS 2022 only)

Support Pack

Link/Description of New Fixed Issues

SP 34

Fixed Issues

SP 33

Fixed Issues

SP 32

Fixed Issues

SP 31

Fixed Issues

SP 30

Fixed Issues

SP 29

1. Windows 10 2004 support
2. VS 2019 Update 7 support
3. HANA 2.0 SP05 support

Fixed issue -  2947850 - Exporting HTML wrapped in text causes Crystal Reports Designer 2016+ and .NET CR for VS SP 27 CR Viewer to crash when exporting to txt format

As of SP 29 we now register the Assemblies into GAC using this folder:

C:\Windows\Microsoft.NET\assembly

Previous versions were placed in this folder:

C:\Windows\assembly

SP 28

Fixed Issues

SP 27

Fixed Issues

1.  Win10 1909
2.  SQL Server 2019
3.  Browser updates (Latest Chrome)

Please note, SP27 “Web Service / XML Data Driver” will be uploaded later, once a known issue is ­­­solved.
Please note, SP27 will not be uploaded to the old Akamai site.

Only 1 public fixed issue - 2889303 - Crystal Reports for Visual Studio SP 26 - Next Page causes Optional Parameter to prompt for value

SP 26

Fixed Issues

1. .NET Framework 3.5.1 is no longer supported, we’d recommend to use .NET Framework 4.5.2.
2. Assembly version of CR .NET and RAS .NET upgrade from 13.0.3500.0 to 13.0.4000.0, user should load their project in VS to migrate the references.
1. FlashControlV71 had been removed and replaced by AxShockwaveFlashObjects and ShockwaveFlashObjects; they’re NOT required to add as reference in project, will be called by CrystalDecisions.Windows.Forms on runtime automatically.
3. There will be problem if application built with .NET Framework 4.0 as target framework and printed to Microsoft XPS Document Writer via ReportDocument.PrintToPrinter API (the same in Winform/WPF Viewer print).
1. Support for .NET Framework 4, 4.5, and 4.5.1 ended on January 12, 2016 per Microsoft
2. To solve this problem, user should target their project to .NET Framework 4.5.2 or above and re-build it.
4. If end-user use in-place upgrading from SP25 or previous version, after upgrading, they must repair the installation in Control Panel/Programs. Otherwise, the ADO.Net database connection will NOT work.
5. The prerequisites Microsoft_VC120_CRT_x86.msm, Microsoft_VC140_CRT_x86.msm and Microsoft_VC140_MFC_x86.msm should be added when using CR Runtime Merge Modules, or used vcredist_x86.exe from Visual C++ Redistributable Packages for Visual Studio 2013 and Visual Studio 2015.
6. Microsoft Windows Update KB2999226 is still required for all OS before the Windows 10/Windows Server 2016.

SP 25

Fixed Issues

SP 24

SP 23

Fixed Issues

SP 22

Fixed Issues

SP 21

Fixed Issues

·       In-place upgrades are no longer supported. Older version of Crystal Reports for Visual Studio must be removed before installing the new version.

·       See KBA for more info -  For Installation issues PLEASE see this KBA -  2536330 - In-place (FlexNet), MSI and Merge Modules upgrade from Crystal Reports for Visual Studio SP xx to SP 21 does not work

·       For more info search for this Kbase article:

·       For reports using the ADO.Net DB connection, in previous SP's, you could only work under .Net Framework 2.0/3.5, so using <startup useLegacyV2RuntimeActivationPolicy="true"> in app.config is required. Now in SP21 and above, ADO.Net is only supported on .Net Framework 3.5 or above and you can remove the tag.

SP 20

1. HANA 2.0 SPS01
2. Addressed 5+ customer Incidents. 

SP 19

1. Windows Server 2016
2. IIS 10 on Windows Server 2016
3. Addressed over 10 customer Incidents.