Problems and solutions generated after installing Crystal Report 9.2, how to migrate .NET programs to Crystal Report 9.2

Problems after installation Crystal Report 9.2 and solutions (Author: Hyperion .NET, update: 2003-10-19) ----------------------- -------------------------------------------------- Directory: 1. Introduction II, concept and principle three, problem 1 2. When copying the Crystal Report Viewer, the Control Create Error is displayed. 3. When you create a Crystal Report Viewer, the Control Create Error is displayed. 4, analyzer error message: Base class includes field "CrystalReportViewer1", but its type is incompatible with the type of Crystaldecision.Web.crystalReportViewer. 5, Analyzer Error Message: Found the program set list of "CRYSTALDECSISIONS.SHARED" not match the assembly reference. 6, problem: invalid report source 7, if you use VS.Net 2003 ... 8, problem: Washing a new project in Web.config, there is no After I have added configuration errors! ! ! -------------------------------------------------- ----------------------- First, in the .NET, DLL Hell Problem is resolved - including metadata, with self-descriptive assembly And its XCopy deployment! However, it seems to bring new issues --.NET program upgrade, migration problems ... upgrade no longer just simply installed, have to do it ... -------------- -------------------------------------------------- --------- Second, concept and principle 1. "Program Version" of various Crystal Reports programs ... Crystal Reports for Visual Studio .NET 2002Crystal Reports Management Components "Program Version" is 9.1.3300 .

Crystal Reports for Visual Studio .NET 2003 Program Crystal Reports Management Component's "Program Version" is 9.1.5000.0.

Crystal Reports 9 program (only for Visual Studio 2002) Crystal Reports Management Components is 9.2.9466.x.

Crystal Reports 9.2 program (file versions "with Visual Studio 2002 and 2003) Crystal Reports management components are 9.2.9500.x. ------------------------------------------------2, The Crystal Report Viewer version in Crystal Report Viewervs.NET is 9.1.3300.0, the Crystal Report Viewer version in Crystal Report 9.2 is 9.2.3300.0 After adding the Crystal Report Viewer to the Form, add the following code in the ASPX file, is missing . Code (1) <% @ Register TagPrefix = "cr" Namespace = "CrystalDecisions.Web" Assembly = "CrystalDecisions.Web, Version = 9.1.3300.0, Culture = neutral, PublicKeyToken = 692fbea5521e1304"%> is provided to introduce namespace CrystalDecisions. Web. Code (2) is a CrystalReportViewer control label. -------------------------------------------------- ----------------------- Third, Question 1, Compiler error message: BC30560: "CrystalReportViewer" in Name Space It is not clear.

------------------------- Problem Analysis: After the Design View deletes Crystal Report Viewer, the code (1) still exists, if this time Add a new version of Crystal Report Viewer, can cause two different code (1): <% @ register tagprefix = "cr1" name "name" asmbly = "Crystaldecisions.Web, Version = 9.2.3300.0, Culture = neutral, PublicKeyToken = 692fbea5521e1304 "%> <% @ Page language =" vb "Codebehind =" Analysis.aspx.vb "AutoEventWireup =" false "Inherits =" Research_VB.Analysis "%> <% @ Register TagPrefix =" cr " Namespace = "Crystaldecisions.Web" Assembly = "Crystaldecisions.Web, Version = 9.1.3300.0, Culture = neutral, publickeyToken = 692fbea5521e1304"%> ------------------------------------------------------------------------------------------------------------------------------------------------------ ----- Solution: Remove the Crystal Report Viewer and all code (1), re-add Crystal Report Viewer. ------------------------------------------------2, When copying the Crystal Report Viewer, "Control Creating Errors" is displayed. -------------------------- When copying the Crystal Report Viewer, the code (1) will not be copied. ------------------------- Solution: Handmade Copy Code (1). ------------------------------------ 3, When you create a Crystal Report Viewer, the Control Create Error is displayed. ------------------------- Question: If you are not a residual code (1), it is a incredible thing ... ---------- --------------- Solution: (1) Delete the Crystal Report Viewer control in "Design View"; (2) Remove Code to "HTML View" (1) (3) Create Crystal Report Viewer; if "Control Creating Errors" is displayed, switch to the HTML view, then switch the "Design" view, automatically recover! ! ! ------------------------------------------------ 4, Analyzer error message: The base class includes field "CrystalReportViewer1", but its type is incompatible with the type of Crystaldecision.Web.crystalReportViewer.

------------------------- Question: Code (1) is not the current version of Crystal Report Viewer ----------- -------------- Solution: Delete Crystal Report Viewer and all code (1), re-add Crystal Report Viewer. ------------------------------------ 5, Analyzer error message: The found list definition named "CrystalDecisions.Shared" is not matched with the assembly reference. Source File: E: /Web/Venditionsystem/web.config line: 15 Context Load Tracking: The following information helps to determine the reason why the assembly "CRYSTALDECSIONS.SHARED" cannot be loaded. ------------------------- Problem Analysis: The assembly CRYSTALDECISIONS.SHARED In Web.Config is defined by cr for vs.net version The project is quoted in the project is CR 9.x version ... ------------------------- Solution 1: New solution, Add a Crystal Report Viewer in the form, automatically generate a new version of the program set list in the web.config, then copy this web.config ... Solution 2: Modify the old version of the old version in Web.config Checklist definition: change Version = 9.1.3300.0 to Version = 9.2.3300.0. ------------------------ Summary: Conflict in other CrystalDecisions assessments, such as: Crystaldecisions.CrystalReports.Engine, Solutions. ------------------------------------------------ 6, Problem: Invalid report source ------------------------- Problem Analysis: ReportDocument, CrystalReportViewer Components and CrystalDecisions assembly are inconsistent: ---- --------------------- Solution: (1) Delete all CRYSTALDECSIONS assembly references; (2) Delete all ReportDocument, CrystalReportViewer components; (3) follow 2. Modify the toolbox settings for Visual Studio.NET; (4) Re-add components to automatically generate new references. ------------------------------------------------ 7, If you use VS.NET 2003 ... Problem: It's okay.

There is no discharge control after the upgrade has no code (1)! ! ! Problem Analysis: If you use VS.Net 2003, Crystal Reports 9 (version 9.2.0.x) cannot run correctly, you need to upgrade to CR 9 (version 9.2.x). The specific problem is as follows: - Add new Reports to the project, but does not generate the corresponding report class file - Add a new report or report viewer (Viewer) to the project, but not automatically add the required reference - unable to create a strong-type report (Strongly-Typed Report) instance solution: Upgrade to CR 9 (version 9.2.2.x). ------------------------------------- ----------- 8, question: No After you add a configuration error! ! ! Solution: Create a solution, add the Crystal Report file and Crystal Report Viewer, then use its web.config to overwrite the original program ... How to migrate the .NET program to Crystal Report 9.2 ...... (Update: 2003-10-15) author: Hyperion .NET) -------------------------------------- 10 new, Problem: Invalid report source added 9. If you use VS.Net 2003, Crystal Reports 9 (version 9.2.0.x) cannot run correctly, you need to upgrade to CR 9 (version 9.2.2.x). -------------------------------------- Introduction: Hope for a long time, based on Web, Crystal report prints, export features have been implemented in Crystal Report 9.2! But after installing Crystal Report 9.2, the original .NET program still cannot own these super practical features, what is the reason? ! In .NET, the DLL HELL problem is resolved - including metadata, has self-descriptive assemblies and its XCOPY deployment! However, it seems to bring new issues --.NET program upgrade, migration problems ... upgrade no longer just simply installed, have to do it ... -------------- ------------------------ Directory 1. Install Crystal Report 9.2 ... 2. Modify Visual Studio.net Toolbox Settings 3, "Older Versions Report file "upgrade ... 4" Older version of the CrystalDecisions program collection "modification ... 5," Web Form file, crystal report namespace reference "upgrade ... 6," Web.config, crystal Report-related assembly "upgrade ... 7, problem: I upgrade CrystalReport9.2, now CrystalReportViewer can not drag and drop on the design view, why? 8. Question: Newly built a project in Web.config, there is no <

Add assembly = "crystaldecisions.crystalreports.Engine, Version = 9.2.3300.0, Culture = neutral, publickeytoken = 692fbea5521e1304" /> 9, problem: It is not. There is no discharge control after the upgrade has no code (1)! ! ! 10, problem: invalid report source ------------------------------------ 1, install Crystal Report 9.2 ... First uninstall the previous version of Crystal Report, such as Crystal Report for vs.net, Crystal Report 9.0 ... and then install! This avoids many problems: -------------------------------------- 2, modify Visual Studio. NET's toolbox setting (1) Right-click "Toolbox", select Custom Toolbox, enter the Custom Toolbox dialog; (2) Select ".NET Framework Components" tab, click "assembly Name "column header, make it sorted according to" assembly name "; (3) Deselect all CRYSTALDECISIONS version of 9.1.xxxx.x; (4) Click" Browse "button, select C: / Program Files / Common files / Crystal Decisions / 2.0 / managed "folder, were added CrystalDecisions.CrystalReports.Engine.dll: adding components ReportDocument, ReportClass, CrystalDecisions.Web.dll: adding components CrystalReportViewerCrystalDecisions.Windows.Forms.dll: adding components CrystalReportViewer-- ------------------------------------ 3, "Older Reports Document" upgrade ... Crystal Report 9.2 Opens a report, make any operation, then revoke, and finally save it, will upgrade the report.

Note: After upgrading, you cannot use the old version of Crystal Decisions products ... -------------------------------- ---- 4, "the old version of CrystalDecisions assembly reference" changes ...... (1) CrystalDecisions assembly: CrystalDecisions.CrystalReports.EngineCrystalDecisions.WebCrystalDecisions.Enterprise.ReportCrystalDecisions.ReportSourceCrystalDecisions.Shared etc ...... (2) storing " Program collection references "file - project file; extension is ?? Proj, for example: C # project extension is csproj original reference, such as CrystalDecisions.web: upgraded references: (3) Modify the" reference path " ": In the Solution Explorer, right click on the project, select Properties, enter the project property page; select General Properties -> Reference Path: C: /Winnt/Assembly/gac/crystaldecisions.Web/9.2.3300.0__692fbea5521e1304 / ------------------------------------ 5, "Web Form file, crystal report namespace reference "Upgrade ... original reference: <% @ regis ter TagPrefix = "cr" Namespace = "CrystalDecisions.Web" Assembly = "CrystalDecisions.Web, Version = 9.1.3300.0, Culture = neutral, PublicKeyToken = 692fbea5521e1304"%> upgraded quote: <% @ Register TagPrefix = "cr" Namespace = "crystaldecisions.web" assembly = "Crystaldecisions.Web, Version = 9.2.3300.0, Culture = neutral, publickeytoken = 692fbea5521e1304"%>

-------------------------------------- 6, "Web.config, Crystal Reports the assembly 'upgrade ...... original quote: ...... upgraded quote: ...... -------------------------------------- 7, questions: I upgrade CrystalReport9.2, now CrystalReportViewer can't drag and drop on the design view, why? Solution: 1. Right-click the tab on "Toolbox", select Custom Toolbox, enter the Custom Toolbox dialog, select ".NET Framework Components" tab; 2, there are four CrystalReportViewers , namely: CrystalDecisions.Web (9.2 ...... CrystalDecisions.Web (9.1 ...... CrystalDecisions.Windows.Forms (9.2 ...... CrystalDecisions.Windows.Forms (9.1 ...... select: CrystalDecisions.Web (9.2 ...... CrystalDecisions.Windows.Forms (9.2 ... removal: Crystaldecisions.Web (9.1 ... Crystaldecisions.windows.Forms (9.1 ... summary: It can be seen that it is 9.2.3300.0 to change to 9.2.3300.0 !!! This, after upgrading the crystal report file, directly Replace all files (web.config, project files, aspx files), OK !!! -------------------------- ------------ 8, Question: Newly built a project in Web.config Nothing After I have added configuration error !!! Solution: New Solution, add Crystal Report Viewer,