Recently both Paul Stovell and Joseph Cooney blogged about one very interesting topic - "Do people really need grid controls in WPF?". They're saying that people actually don't need grids in WPF and this is what makes their blog posts worth reading. Imagine if they had said the opposite: "People need grid controls for WPF!". It would have been quite boring and wouldn’t have spurred much of a discussion. For many people the idea of not having grids for WPF sounds unconventional but Paul made an interesting parallel to justify his claim "Using grids in WPF is like buying a Ferrari to pick up...

After more than fifteen hours of flights across half of the world, I finally had a chance to get some sleep. After a few cups of coffee, I am finally catching up with e-mail and everything else that happened in the office during TechEd. It was a great week and I want to say a big “THANK YOU” to all of you who attended the Telerik booth at TechEd 2008 in Orlando. The positive feedback we got from you guys was incredible! It was great fun to see how many people were wearing .NET Ninjas and Geekettes and I was really surprised to discover that some of the attendees were wearing...

Hi everyone, by means of introduction my name is Martin Vassilev and I am a support officer with the Windows Forms team here at Telerik. As of late, we noticed increased interest towards RadGridView data export capabilities. What we have always told our customers is that the RadGridView will have only basic Microsoft Excel export capability, until we are able to implement a commercial grade format converter here at Telerik. However, that requires quite some time, and customers can’t wait right? What was needed was a quick, easy, stable way of exporting RadGridView content to formats such as RTF, PDF and...

I visited DevConnections in Orlando about a month ago. There my colleague Todd Anglin and I held a vendor session called "Developing Rich, Responsive Applications using Telerik RadControls for ASP.NET AJAX". My team had prepared a demo for the vendor session - and we have 3 major goals when we started implementing it: We wanted to keep the code to a minimum (which I think we managed quite nicely). Most of the about 200 lines of server code are related to database queries, and the client-side only uses about 40 lines of code. We wanted it to be real life and do...

If you are familiar with WPF you are aware that the the grand daddy of all controls is FrameworkElement. It is defined in the PresentationFramework.dll assembly and derives from UIElement (defined in PresentationCore.dll). Its purpose is to serve as a base element for all framework related stuff: styles, inheritance context, etc. However there is another framework element - FrameworkContentElement. The main distinct between them is that the later did not defines its own rendering behavior (its inheritors should do so). This is way properties like: (Actual)Width or (Actual)Height are not present at FrameworkContentElement. If you examine the classes that derive from FrameworkContentElement...