Sap Crystal Reports Version For Microsoft Visual Studio



Crystal Reports, version for Visual Studio is a developer tool offered as a free add-on for Microsoft Visual Studio. Crystal Reports, version for Visual Studio is a developer tool offered as a free add-on for Microsoft Visual Studio. Javascript must be enabled for the correct page display. SAP Crystal Reports, developer version for Microsoft Visual Studio: Updates & Runtime Downloads Follow RSS feed Like 113 Likes 5,010,791 Views 6 Comments. SAP Crystal Reports, upgrade version Choose this discounted version if you’re running an older version of SAP Crystal Reports and want to upgrade. Migrating old report files (.rpt) from SAP Crystal Reports 9 to SAP Crystal Reports 2016 with SAP Crystal Reports 2020 is usually easy: Open, check data connection (s), then Save.

SAP Crystal Reports, version for Visual Studio

Technical & License Resources


Technical Details

Product: SAP Crystal Reports, version for Visual Studio 2010
Data sources: ODBC, OLE DB, Access, Excel, ADO.NET, CDO, IDataReader, DAO, RDO, XML and file-based data sources
License model: When using SAP Crystal Reports, version for Visual Studio .NET you may:

  • Design reports for use in .NET applications
  • Design reports for thick-client Windows applications
  • Design reports for server applications


System Requirements

Product prerequisites: SAP Crystal Reports, version for Visual Studio .NET 2010
Processor: 1.6 MGHz or faster
Memory: 1GB (32-bit) or 2GB (64-bit) RAM
Disk space: 650MB (32-bit) or 1.1GB (64-bit) available
Operating systems: Windows 2003, Windows XP, Windows Vista Platform
Support: Windows


Licensing:


Design Reports for Use in .NET Applications


The SAP Crystal Reports, version for Visual Studio 2010 report designer is fully integrated within Microsoft Visual Studio 2010 for powerful and easy report design. You may use the integrated designer to create an unlimited number of reports for use within your .NET applications.


Reporting for Thick-Client Windows Applications


The SAP Crystal Reports, version for Visual Studio .NET 2010 runtime engine can be integrated into thick-client Windows applications to add reporting capabilities.


A thick-client Windows application is any application in which the SAP Crystal Reports, version for Visual Studio .NET 2010 runtime engine is installed and run from the end user's client machine.


You are free to deploy thick-client Windows applications that embed the runtime engine. These applications can be freely deployed both within your own organization and redistributed outside your organization to third parties at no additional charge.

Crystal Reports For Visual Studio Download


Distribution of the runtime engine is subject to the terms and conditions contained in the SAP Crystal Reports, version for Visual Studio 2010 License Agreement.


Reporting for Server Applications


A server application allows more than one user to access the reporting engine either directly or indirectly through any middle tier application.


You are free to deploy server applications that embed the runtime engine internally within your organization at no additional charge.

Sap Crystal Reports Redistributable


To deploy server applications to third parties, written authorization from SAP is required. You can get authorization by registering your application online at no extra cost.


Sap


Scaling Server Applications


The SAP Crystal Reports, version for Visual Studio runtime engine included with Visual Studio 2010 is designed to support small applications. Each version of Visual Studio has slight differences on how it handles multiple requests.


  • Visual Studio 2003 – If you exceed the throughput limitations, the runtime engine will generate an exception. To add queuing and many other functional features to your Visual Studio 2003 application, upgrade to SAP Crystal Reports 2011.
  • Visual Studio 2005, 2008 and 2010 – Requests to the runtime engine that exceed the throughput limitations will queue until a thread becomes available to process it.
  • Supporting larger applications – Depending on your requirements, several options are available for increased scalability and functionality. Regardless of your choice, upgrading is straightforward and requires minimal code changes. Learn more
Skip to end of metadataGo to start of metadataPurpose

This is a list of fixed issues in Service Pack 15 for Crystal Reports for Visual Studio (CRVS).

Overview

This wiki documents 5 issues and 3 Enhancement Requests that have been addressed in Service Pack 15 for CRVS. The issues are documented in individual KBases. For details, see the table under the List of Fixed Issues heading. “SAP Crystal Reports, developer version for Microsoft Visual Studio” can be used with Visual Studio 2010 to 2013 as well as Visual Studio 2015.

Sap

New in this Release

  1. Added support for Visual Studio 2015 RC.
  2. Added an easy way to use Print Output Control in WinForm Viewer.
  3. Addressed several Incidents.
  4. Support for FireFox ESR 38.

Where to Download Service Pack 15

Service Pack 14 for “SAP Crystal Reports, developer version for Microsoft Visual Studio” can be downloaded using the links documented in the Document SAP Crystal Reports, developer version for Microsoft Visual Studio Updates & Runtime Downloads. The Document includes links for the runtime MSM, MSI files and more. Developer Help files can be downloaded from the following links

List of Fixed Issues - Note: SAP is no longer using Adapt - SAP Note will have link to Work Bench ID

2051790 1916075
Synopsis
SAP Note ID
Incident 663010PrintOutputController printmode from viewer does not print/export the tab view2209712
Incident 577155Error in Conditional Formula no longer generates a valid .NET SDK error message2194352

Incident 508399

VS 2015 Community not detected

2181302
Incident 205148Get Saved XLSX Export options gen Exception2181164
Incident N/APrinter Tray in the new POC feature did not use what was saved in the report

Issue has been found - Located in the crystalreportsviewer13 folder under the framework there is a crviewer.aspx file. Delete ALL copies of it. It is not required and can cause bobj not defined and possibly an AllInOne error in WEB applications.

Installing onto Windows 10 x86 format indicates there is no VS installed - as a temporary workaround create the 64 bit regsitry key the installer is looking for:

HKLMSOFTWAREWow6432NodeMicrosoftDevDivvsServicing14.0professional

Create key named “Install” REG_DWORD and value as 1

For Web applications and Framework 4.x updates with 4.6 installed the CR Viewer folder will get a 4_6_xxx added to the path.

To work around this copy the CrystalReportViewer13 folder to your project and add the following to your web.config file:

We discovered as soon as you update your version of 4.6 framework it's going to rename the folder being used.

Work around now is to do this...

add the CrystalReportViewer13 folder to your project, copy it into you app folder. then update your web.config file with the following:

<configSections>

<sectionGroup name='businessObjects'>

<sectionGroup name='crystalReports'>

<section name='crystalReportViewer' type='System.Configuration.NameValueSectionHandler'/>

<section name='rptBuildProvider' type='CrystalDecisions.Shared.RptBuildProviderHandler, CrystalDecisions.Shared, Version=13.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304, Custom=null'/>

</sectionGroup>

</sectionGroup>

</configSections>

<businessObjects>

<crystalReports>

<crystalReportViewer>

<add key='ResourceUri' value='/crystalreportviewers13'/>

</crystalReportViewer>

</crystalReports>

</businessObjects>

<appSettings>

...

This will redirect all requests to that viewers folder.


Related Documents