I just downloaded the latest version of the Reporting tools and noticed that it did not install a Telerik.Reporting.XamlRendering.dll this time. In the instructions for deploying a WPF application, it still says to include this dll but I don't have it in the reporting dlls or the WPF controls dlls. Just want to verify that I didn't get something installed incorrectly before I get too far.
thanks!
thanks!
4 Answers, 1 is accepted
0
Hi Koren,
The Q1 2011 SP1 release of Telerik Reporting has a completely reworked XAML rendering extension. The new rendering extension uses a lightweight approach for generating XAML that is more suitable for highly concurrent multi-threading server applications. As a result XAML rendering no longer depends on any .NET 3.5 assemblies at all and for this reason it is now merged in the main Telerik.Reporting.dll assembly, which depends on .NET 2.0 framework. Only the XPS rendering extension relies upon certain types from .NET 3.5, so it resides in its own assembly: Telerik.Reporting.XpsRendering.dll. If you use our Upgrade Wizard to migrate to the new version it should take care of this change automatically for you.
Regards,
Chavdar
the Telerik team
The Q1 2011 SP1 release of Telerik Reporting has a completely reworked XAML rendering extension. The new rendering extension uses a lightweight approach for generating XAML that is more suitable for highly concurrent multi-threading server applications. As a result XAML rendering no longer depends on any .NET 3.5 assemblies at all and for this reason it is now merged in the main Telerik.Reporting.dll assembly, which depends on .NET 2.0 framework. Only the XPS rendering extension relies upon certain types from .NET 3.5, so it resides in its own assembly: Telerik.Reporting.XpsRendering.dll. If you use our Upgrade Wizard to migrate to the new version it should take care of this change automatically for you.
Regards,
Chavdar
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items
0
Sergey
Top achievements
Rank 1
Rank 1
answered on 05 Aug 2011, 02:51 PM
I ran the Upgrade wizard on both silverlight and WCF projects. Now I reference v.5.1.11.713 everywhere (Telerik.ReportViewer.Silverlight.dll on client and Telerik.Reporting.dll + Telerik.Reporting.Service.dll on server).
I still get "XAML rendering format is not available".
This help article is not usefull: http://www.telerik.com/help/reporting/installation-deploying-on-silverlight-application.html
Thanks,
Sergey
I still get "XAML rendering format is not available".
This help article is not usefull: http://www.telerik.com/help/reporting/installation-deploying-on-silverlight-application.html
Thanks,
Sergey
0
Hi Sergey,
Usually the Silverlight application is hosted in another project e.g. web site or web application. So you should look in the respective article: Deploying Web Applications. The XAML rendering is now part of the Telerik.Reporting.dll, my colleague has provided the details in previous reply. Additionally you should remove the Telerik.Reporting.XamlRendering.dll assembly from the bin folder to avoid type mismatches.
All the best,
Steve
the Telerik team
Usually the Silverlight application is hosted in another project e.g. web site or web application. So you should look in the respective article: Deploying Web Applications. The XAML rendering is now part of the Telerik.Reporting.dll, my colleague has provided the details in previous reply. Additionally you should remove the Telerik.Reporting.XamlRendering.dll assembly from the bin folder to avoid type mismatches.
All the best,
Steve
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get now >>
0
Sergey
Top achievements
Rank 1
Rank 1
answered on 05 Aug 2011, 03:21 PM
Hi Steve,
Thank you,
Sergey
Deleting Telerik.Reporting.XamlRendering.dll fixed the problem. That’s why I need to know what should be in SL/bin, SL.Web/bin and so on.
Thank you,
Sergey