Error 895 |
The type 'Telerik.ReportViewer.WebForms.ReportViewer' exists in both 'c:\Windows\assembly\GAC_MSIL\Telerik.ReportViewer.WebForms\4.0.10.423__a9d7983dfcc261be\Telerik.ReportViewer.WebForms.dll' and 'c:\Windows\assembly\GAC_MSIL\Telerik.ReportViewer.WebForms\2.9.9.202__a9d7983dfcc261be\Telerik.ReportViewer.WebForms.dll' |
D:\Projects\VS2010\CPRWebPortal_V3\WebPortal\Dashboard\RevenueGenerated.aspx |
I need to have both versions of Reporting on my development pc, using the older v2.9.9.202 for vs2008 projects, and v4.0.10.423 for new vs2010 projects. How must I reseolve the GAC issue?
Dan
6 Answers, 1 is accepted
Dan
We have not been able to reproduce the problem with the missing Upgrade Wizard option in the Telerik menu. Can you confirm that you have a project that contains Telerik Reporting present in the solution?
As for the original reported error, here is a list to check (since you state the upgrade wizard is not working for you):
- Remove all references to Telerik Reporting 2.9.9.202 from your application i.e. register directive or resx file.
- Remove assembly references to Telerik Reporting 2.9.9.202 from your web.config - check the <assemblies> section of your web.config file, and make sure that you are not referencing v. 2.9.9.202 in the VS2010 solution where you want only the Q1 2010 version.
- Ensure that there are assembly references to Telerik Reporting Q1 in your web.config or that the needed assemblies are present in the bin folder of your web site.
If you are still having problems, please open a support ticket, zip and attach a sample VS2010 project using version 4.0.10.423 which replicates the issue when we have 2.9.9.202 installed as well. Once we review it, we would be able to provide more info as to why it is happening.
All the best,
Steve
the Telerik team
I have resolved the duplicate GAC compile problems. I had to manually edit each of my .resx files and change the Reporting version in the code there. Then the compile errors went away. I still have some issues to resolve with the Reporting code, having some problem with the ReportParameters not working. But I haven't had time to look into that yet.
I don't know why I have no Telerik Reporting menu in VS2010. Could it be that when installing the new Telerik Reporting, it "found" the instance of VS2008 and updated it, but then stopped, and did not "find" VS2010?
If I had the Report Wizard in VS2010, would it fix the 900+ warnings that I have for:
Telerik.Reporting.ReportParameterUISettings.Visible' is obsolete: 'Please use the ReportParameter.Visible property instead.
Thanks,
Dan
The setup of Telerik Reporting detects what versions of Visual Studio you have (see attached screenshot) and installs the Reporting templates into all detected (unless you've chosen otherwise).
The obsolete properties are not handled by Telerik Reporting wizards - they should be updated manually by the developer. You can use a mass search and replace for this specific change.
Greetings,
Steve
the Telerik team
Hello.
I had the same problem.
I upgraded telerik reporting from Q1 2010 to Q2 2010. Then in my VS2010 i executed Telerik->Reporting->Upgrade Wizard and upgraded to Q2 2010. In my solution i have silverlight reporting and ASP.NET reporting. It was odd at first that silverlight reporting worked OK but ASP.NET reporting failed with error as in this post (2 GAC versions).
I checked my ASP.NET BIN folder and there i found OLD Telerik.ReportViewer.WebForms.dll files (files had old dates) but in silverlight bin folder there was correctly dated Telerik.ReportViewer.Silverlight.dll file.
I then simply copied correct (newest) Telerik.ReportViewer.WebForms.dll file into my ASP.NET bin project folder (and also did another reference to the new dll) and "2 GAC versions" error went away. It seems like telerik wizard somehow "failed" to copy dlls into asp.net project but it copied dlls into silverlight project.
Actually the Upgrade Wizard does not copy assemblies. It only changes references to the new ones and if you have manually copied assemblies into your bin folder - they would not be altered. The reason why you're left with the impression that it works this way for the Silverlight viewer is the fact that all relevant assemblies are embedded into the XAP file at compile time.
Regards,
Steve
the Telerik team