Crystal Reports Deploying Instructions
-
Upload
davy-jones -
Category
Documents
-
view
468 -
download
2
Transcript of Crystal Reports Deploying Instructions
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 1
Deploying Crystal Reports for
Visual Studio 2010 Beta
Applies to:
Crystal Reports for Visual Studio 2010 Beta, Crystal Reports 2008 SP2. For more information, visit the Interoperability - .NET homepage.
Summary
This document provides information on how to use the Crystal Reports 2008 redistributable packages to deploy a Microsoft Visual Studio 2010 project that embeds the Crystal Reports for Visual Studio 2010 Beta release.
Author: Mandeep Jassal
Company: SAP Business Objects
Created on: 5 April 2010
Author Bio
Mandeep Jassal works as a Program Manager on the Enterprise Reporting team at SAP. His team works on the Crystal Reports products.
Deploying Crystal Reports for Visual Studio 2010 Beta
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 2
Table of Contents
Overview ............................................................................................................................................................. 3
Getting Started ................................................................................................................................................ 3
Configuring Your Crystal Reports WinForm Application for Deployment ....................................................... 3
Configuring Your Crystal Reports Web Site Project for Deployment .............................................................. 5
Information on Other Relevant Assemblies .................................................................................................... 6
Deploying Your Application ............................................................................................................................. 7
Known Issues ..................................................................................................................................................... 8
Related Content .................................................................................................................................................. 9
Copyright ........................................................................................................................................................... 10
Deploying Crystal Reports for Visual Studio 2010 Beta
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 3
Overview
Crystal Reports for Visual Studio 2010 (CR for VS2010) Beta is intended to be used on a test development computer to try out the new version of the developer offering; and therefore, does not provide the runtime redistributable packages required to deploy your VS 2010 application. However, if you would like to deploy your VS 2010 application that embeds the CR for VS2010 Beta product, then you do have a solution.
The Crystal Reports 2008 (CR 2008) runtime redistributable packages can be used deploy your CR for VS 2010 application to client machines. This is mainly possible due to the fact that the .RPT file format has changed very little between the 2 releases. You will need to configure your application in order to use the CR 2008 runtime with your CR for VS2010 application. The details in this document provide information on how to configure your VS 2010 application.
Note: When the final version of CR for VS 2010 is released, it will include updated redistributable packages. Using the CR 2008 redistributable packages will no longer be a supported solution.
Getting Started
Before starting, you need to have Microsoft Visual Studio 2010 and the Crystal Reports for Visual Studio
2010 Beta installed on your computer. The information below assumes that a simple VS2010 Windows
Forms or Web Site project is created.
1. Download the CR 2008 redistributable package from the SAP website and save them to a folder on
your local computer. Click the following link and scroll down until you see the “CR 2008 (SP2)” row
and click the first “Download Link” hyperlink. This will start the download for the CR 2008 .NET
runtime redistributable package (cr2008sp2_redistinstall.zip).
a. https://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=56787567
2. Extract t the downloaded file to your computer. Take note of where you have extracted the
redistributable packages to so that you can find them later. This .zip packages provides 2 files,
CRRuntime_12_2_mlb.exe and CRRuntime_12_2_mlb.msi; only one will be required.
3. Load Visual Studio 2010 and open your solution.
Configuring Your Crystal Reports WinForm Application for Deployment
In order for your application to load the CR 2008 runtime, you must configure the application to load the
correct version of the Crystal Reports assemblies. The steps below provide the details for how to properly
configure your WinForm application to load the CR 2008 runtime. In these steps, we provide information on
how to load the most commonly used assemblies. If you require other assemblies, please reference the
table in the “Information on Other Relevant Assemblies” section for details on the appropriate assembly
name, oldVersion, and newVersion parameters in the configuration file.
1. Open your project‟s configuration (.config) file. Consult Visual Studio documentation on how to
modify the configuration file for your project.
2. Add the following configuration settings to the .config file. These settings should be placed between
the <configuration></configuration> attributes, as shown.
Deploying Crystal Reports for Visual Studio 2010 Beta
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 4
<configuration>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="CrystalDecisions.CrystalReports.Engine"
publicKeyToken="692fbea5521e1304" culture=""/>
<bindingRedirect oldVersion="14.0.2000.0" newVersion="12.0.2000.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="CrystalDecisions.Shared"
publicKeyToken="692fbea5521e1304" culture=""/>
<bindingRedirect oldVersion="14.0.2000.0" newVersion="12.0.2000.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="CrystalDecisions.ReportSource"
publicKeyToken="692fbea5521e1304" culture=""/>
<bindingRedirect oldVersion="14.0.2000.0" newVersion="12.0.2000.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="CrystalDecisions.Windows.Forms"
publicKeyToken="692fbea5521e1304" culture=""/>
<bindingRedirect oldVersion="14.0.2000.0" newVersion="12.0.2000.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="CrystalDecisions.Enterprise.Framework"
publicKeyToken="692fbea5521e1304" culture=""/>
<bindingRedirect oldVersion="14.0.2000.0" newVersion="12.0.1100.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="CrystalDecisions.Enterprise.InfoStore"
publicKeyToken="692fbea5521e1304" culture=""/>
<bindingRedirect oldVersion="14.0.2000.0" newVersion="12.0.1100.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>
</configuration>
Note: If your project contains references to other Crystal Reports assemblies, add them to the configuration using the same format as shown above.
Once you have configured your application to load the CR2008 runtime, you can now deploy it to your client
computer.
Deploying Crystal Reports for Visual Studio 2010 Beta
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 5
Configuring Your Crystal Reports Web Site Project for Deployment
In order for your application to load the CR 2008 runtime, you must configure the application to load the
correct version of the Crystal Reports assemblies. The steps below provide the details for how to properly
configure your Web Site project to load the CR 2008 runtime. In these steps, we provide information on how
to load the most commonly used assemblies. If you require other assemblies, please reference the table in
the “Information on Other Relevant Assemblies” section for details on the appropriate assembly name,
oldVersion, and newVersion parameters in the configuration file.
3. Open your project‟s configuration (.config) file. Consult Visual Studio documentation on how to
modify the configuration file for your project.
4. Add the following configuration settings to the .config file. These settings should be placed between
the <configuration></configuration> attributes, as shown.
<configuration>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="CrystalDecisions.CrystalReports.Engine"
publicKeyToken="692fbea5521e1304" culture=""/>
<bindingRedirect oldVersion="14.0.2000.0" newVersion="12.0.2000.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="CrystalDecisions.Shared"
publicKeyToken="692fbea5521e1304" culture=""/>
<bindingRedirect oldVersion="14.0.2000.0" newVersion="12.0.2000.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="CrystalDecisions.ReportSource"
publicKeyToken="692fbea5521e1304" culture=""/>
<bindingRedirect oldVersion="14.0.2000.0" newVersion="12.0.2000.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="CrystalDecisions.Web"
publicKeyToken="692fbea5521e1304" culture=""/>
<bindingRedirect oldVersion="14.0.2000.0" newVersion="12.0.2000.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="CrystalDecisions.Enterprise.Framework"
publicKeyToken="692fbea5521e1304" culture=""/>
<bindingRedirect oldVersion="14.0.2000.0" newVersion="12.0.1100.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="CrystalDecisions.Enterprise.InfoStore"
publicKeyToken="692fbea5521e1304" culture=""/>
<bindingRedirect oldVersion="14.0.2000.0" newVersion="12.0.1100.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>
</configuration>
Note: If your project contains references to other Crystal Reports assemblies, add them to the configuration using the same format as shown above.
Deploying Crystal Reports for Visual Studio 2010 Beta
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 6
Once you have configured your application to load the CR2008 runtime, you can now deploy it to your client
computer.
Information on Other Relevant Assemblies
This section provides the necessary assembly names, oldVersion, and newVersion parameter values for other relevant assemblies that you may want to add to your projects
Assembly Name Old Version New Version
CrystalDecisions.CrystalReports.Design 14.0.2000.0 12.0.2000.0
CrystalDecisions.CrystalReports.Engine 14.0.2000.0 12.0.2000.0
CrystalDecisions.CrystalReports.TemplateEngine 14.0.2000.0 12.0.1100.0
CrystalDecisions.Data.AdoDotNetInterop 14.0.2000.0 12.0.2000.0
CrystalDecisions.Enterprise.Framework 14.0.2000.0 12.0.1100.0
CrystalDecisions.Enterprise.InfoStore 14.0.2000.0 12.0.1100.0
CrystalDecisions.ReportAppServer.ClientDoc 14.0.2000.0 12.0.1100.0
CrystalDecisions.ReportAppServer.CommLayer 14.0.2000.0 12.0.1100.0
CrystalDecisions.ReportAppServer.CommonControls 14.0.2000.0 12.0.1100.0
CrystalDecisions.ReportAppServer.CommonObjectModel 14.0.2000.0 12.0.1100.0
CrystalDecisions.ReportAppServer.Controllers 14.0.2000.0 12.0.1100.0
CrystalDecisions.ReportAppServer.CubeDefModel 14.0.2000.0 12.0.1100.0
CrystalDecisions.ReportAppServer.DataDefModel 14.0.2000.0 12.0.1100.0
CrystalDecisions.ReportAppServer.DataSetConversion 14.0.2000.0 12.0.1100.0
CrystalDecisions.ReportAppServer.ObjectFactory 14.0.2000.0 12.0.1100.0
CrystalDecisions.ReportAppServer.Prompting 14.0.2000.0 12.0.1100.0
CrystalDecisions.ReportAppServer.ReportDefModel 14.0.2000.0 12.0.1100.0
CrystalDecisions.ReportAppServer.XmlSerialize 14.0.2000.0 12.0.1100.0
CrystalDecisions.ReportSource 14.0.2000.0 12.0.2000.0
CrystalDecisions.Shared 14.0.2000.0 12.0.2000.0
CrystalDecisions.VSDesigner 14.0.2000.0 12.0.2000.0
CrystalDecisions.Web 14.0.2000.0 12.0.2000.0
Deploying Crystal Reports for Visual Studio 2010 Beta
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 7
Deploying Your Application
Using the redistributable package downloaded in the “Getting Started” section, you can now deploy your
Crystal Reports for Visual Studio 2010 Beta project.
1. On your client computer, install the CR 2008 runtime. You can copy and execute (double-click and
run) the CRRuntime_12_2_mlb.msi (or CRRuntime_12_2_mlb.exe) redistributable package on the
client computer, or execute the redistributable package from a network location from the client
computer. This will install the CR 2008 runtime files on the client computer.
a. Once the CR 2008 runtime is installed, copy the „crystalreportviewers12‟ folder from the
„C:\Inetpub\wwwroot\aspnet_client\system_web\2_0_50727‟ folder to the
„C:\Inetpub\wwwroot\aspnet_client\system_web\4_0_30319‟
2. Deploy your application to the client computer. Visual Studio offers many ways to deploy your
application to client computers, and can differ between Windows Forms and ASP.NET Web Site
applications.
a. To deploy Windows Forms applications, the common way is to use a Setup project to build
an MSI install package for your application. Once the MSI install package is created, you
can execute it on the client computer.
b. To deploy ASP.NET Web Site applications, a Setup project can be used (just like for
Windows Forms projects) but Visual Studio allows you to publish your ASP.NET project to
the client computer where an IIS server has been installed.
c. For more information on deploying Visual Studio applications, please consult Visual Studio
documentation.
Once your application and the CR 2008 runtime have been installed, you can run your application and it will
now view reports using the CR2008 runtime.
CrystalDecisions.Windows.Forms 14.0.2000.0 12.0.2000.0
Deploying Crystal Reports for Visual Studio 2010 Beta
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 8
Known Issues
There are known issues that come with using the CR 2008 runtime with your CR for VS 2010 projects. The following items will explain and help with these issues.
1. If your project references the following components, remove them from the project. CR for VS 2010 includes components that were not included with the CR 2008 runtime and may cause errors at runtime if they are still referenced in your VS 2010 project.
a. Log4net b. CrystalDecisions.PromptingClientSDK
2. If the web.config file has the configuration attribute, xmlns=http://schemas.microsoft.com/.NetConfiguration/v2.0, then remove it and save the web.config file. Including this attribute may cause runtime errors related to not finding the CR assemblies with version 14.0.2000.0.
Deploying Crystal Reports for Visual Studio 2010 Beta
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 9
Related Content
Crystal Reports 2008 Developer Guide
For more information, visit the Interoperability - .NET homepage.
Deploying Crystal Reports for Visual Studio 2010 Beta
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 10
Copyright
© Copyright 2010 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.