New 10, problem: invalid report source
New 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:
I have been looking forward to the WEB-based, crystal report printing, export function has 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 problem ...
Upgrade is no longer just simple installation, there is a job that has to be done ...
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
table of Contents
1, install Crystal Report 9.2 ......
2, modify the toolbox settings for Visual Studio.net
3. The upgrade of "old version of the report document" ...
4. Modification of "Older version of CrystalDecisions program collection ...
5, "WEB form file, crystal report namespace reference" upgrade ......
6, "Web.config, Crystal Report-related assembly" upgrade ......
7. Question: I upgraded CrystalReport9.2, now CrystalReportViewer is not dragged and dropped on the design view, why?
8. Question: No
9. Question: 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 ...
Then install it!
This avoids many problems:
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
2, modify the toolbox settings for Visual Studio.net
(1) Right-click "Toolbox", select Custom Toolbox, and enter the Custom Toolbox dialog box;
(2) Select the ".NET Framework Components" tab, click the "Squiry Name" column header to sort it according to the "assembly name";
(3) Deselect All CRYSTALDECISIONS versions of 9.1.xxxx.x;
(4) Click the "Browse" button, select "C: / Program Files / Common Files / Crystal Decisions / 2.0 / Managed" folder, add
CrystalDecisions.crystalReports.Engine.dll: Add Component ReportDocument, ReportClass, Crystaldecisions.Web.dll: Add Components CrystalReportViewer
CrystalDecisions.windows.Forms.dll: Add Component CrystalReportViewer
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
3. The upgrade of "old version of the report document" ...
Use Crystal Report 9.2 to open the report, make any operation, then revoke, finally saved, will upgrade the report.
Note: After upgrading, you cannot use the old version of the Crystal Decisions product ...
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
4. Modification of "Older version of CrystalDecisions program collection ...
(1) CrystalDecisions assembly:
Crystaldecisions.crystalReports.Engine
CrystalDecisions.Web
CrystalDecisions.Enterprise.Report
Crystaldecisions.reportsource
CrystalDecisions.shared
and many more……
(2) Store the "assembly reference" file - project file; extension is ?? Proj, for example: C # project extension is csproj
Original reference, such as Crystaldecisions.Web:
Name = "crystaldecisions.web" AskEMBLYNAME = "CrystalDecisions.Web" Hintpath = "../../../winnt/assembly/gac/crystaldecisions.web/9.1.3300.0__692fbea5521e1304/crystaldecisions.web.dll /> References after upgrading: Name = "crystaldecisions.web" AskEMBLYNAME = "CrystalDecisions.Web" Hintpath = "../../../winnt/assembly/gac/crystaldecisions.web/9.2.3300.0__692fbea5521e1304/crystaldecisions.web.dll /> (3) Modify the "reference path" of the project: In the Solution Explorer, right click on the item, select Properties, and 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: <% @ Register TagPrefix = "cr" Namespace = "CrystalDecisions.Web" Assembly = "CrystalDecisions.Web, Version = 9.1.3300.0, Culture = neutral, PublicKeyToken = 692fbea5521e1304"%> references upgraded: <% @ Register tagprefix = "cr" namespace = "Crystaldecisions.Web" assembly = "Crystaldecisions.Web, Version = 9.2.3300.0, Culture = neutral, publickeyToken = 692fbea5521e1304"%> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 6, "Web.config, Crystal Report-related assembly" upgrade ...... Original reference: ...... References after upgrading: ...... ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 7. Question: I upgraded CrystalReport9.2, now CrystalReportViewer is not dragged and dropped on the design view, why? solution: 1. Right-click the tab on the Toolbox, select Custom Toolbox, go to the Custom Toolbox dialog box, select the ".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 ... Remove: Crystaldecisions.Web (9.1 ... Crystaldecisions.windows.Forms (9.1 ... to sum up: It can be seen that it is achieved 9.1.3300.0 to 9.2.3300.0! ! ! In this way, after upgrading the crystal report file, replace all files (web.config, project file, aspx file), OK! ! ! ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 8. Question: No I have a configuration error after I add! ! ! solution: Create a solution, add Crystal Report Viewer, then use its web.config to overwrite the original program ... ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 9. Question: It is not. 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.2.x). The specific problems are as follows: - Add new reports to the project, but does not generate corresponding report class files - Add new reports or report viewers (Viewer) to the project, but do not automatically add required references - Can't create a strong-type report (Strongly-Typed Report) solution: Upgrade to CR 9 (version 9.2.2.x). ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 10, problem: invalid report source problem analysis: ReportDocument, CrystalReportViewer Components and CrystalDecisions assembly are inconsistent: Solution: (1) Remove all CrystalDecisions 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.
