• .NET

    Setting custom skin for the web report viewer

    I've been asked a few times by clients how to customize the web report viewer's skins, so they can better match their company identity. I would try to describe 'the process' in this post. We are trying to stay close to the approach used for the RadControls for ASP.NET AJAX, so one who has used our web controls would be pleasantly surprised to find two familiar properties in Telerik Reporting - Skin and SkinsPath. As their names suggest, the first one is used to specify the name of the skin, while the second one specifies the path where this skin can be found. Let's start with...
  • .NET

    Telerik Reporting Q1 2009 SP1 is now live

    Once again our constant urge to provide you with the Telerik quality you're used to, resulted in Q1's first service pack of Telerik Reporting. It's needless to say that it contains important bug fixes and improvements of the product and to our new "players" - the Table and HtmlTextBox items. Here is a brief overview: Added support for multi-page view in the Win Report Viewer - although it is not common to include new functionality for a service pack, we decided to push this through instead of making you wait for the Q2 release. This has been long awaited feature for many of you, so do give it a spin. Next thing...
  • .NET

    Connecting the Dots: ADO.NET Data Services and Telerik Reporting

    April 24, 2009 Share
    ADO.NET Data Services (formerly Astoria) is one of the new technologies released as part of v3.5 SP1 of the .NET Framework. If you haven’t tried this new addition to the framework, I highly suggest you give it a spin. It’s very cool and allows you to quickly and easily set up RESTful WCF services with which your application can interact with the database. If you’re interested in learning more, MSDN has several great resources to help you get started. One of the cool things about Telerik is that the developers are always mindful of building products that can be easily integrated with existing and future...
  • .NET

    Free Whitepaper: Understanding the What, Why and How of Reporting Solutions

    Often we see requests from our Telerik Reporting clients to produce PDF or HTML representations of tabular data in order to be able to print the data on paper and/or to create a document. Although this is a common scenario, the proper tool or product has to be used in order to get the best possible results. Telerik Reporting supports these document formats, but often it is mistaken for a format conversion tool (say HTML to PDF), rather than a report generation tool, only because it supports these two formats. We also see a common misconception that Telerik Reporting is...
  • .NET

    Telerik Reporting: Connecting to Stored Procedures

    March 14, 2009 Share
    I’ve blogged in the past about the many ways you can connect your reports to data. Because the developers who build Telerik’s Reporting Tool wanted to make it as flexible as possible, they designed it to have the ability to bind to any object that implements one of the four supported interfaces: IEnumerable, IListSource, ITypedList, and IDbDataAdapter. What does this mean for you? No matter where your data comes from – plain SQL queries, stored procedures, web services, etc – you can bind it to a Telerik report. Okay, I realize that showing an example is much more effective than just talking...