As you may know Telerik has built into most of its products support for Windows and SQL Azure. While at the PDC last November, Ben Riga interviewed me on what it was like to build a commercial product on top of Azure. I give a sneak peak at how we developed the software and how we leveraged SQL Azure. I talk about some of our pain points as well as where it was easy. The video is here, complete with my cell phone’s battery dying in the middle of our interview! Enjoy! Technorati Tags: Azure,Telerik

As people become more aware of the fantastic things you can do with Silverlight, they’ve also realized one of the downsides of this can be increased XAP size.  The default way that Silverlight handles a XAP is to include all the required assemblies into that single compressed file.  This isn’t that bad when you’re working with a barebones Silverlight project, but once you start adding in different controls or 3rd party assemblies you are increasing your XAP size quite a bit in some cases.  And as we all know, a larger XAP leads to longer load times, and although people have...

    The feedback about our new version of CoverFlow for Silverlight has been great! Thank you guys for pointing out all these small issues and problems that had to be polished since we introduced a new beta CoverFlow for Silverlight 3 back in September. After the core functionality of the control is successfully integrated in our Silverlight 3 suite, we are now able to start developing new features that every grown-up CoverFlow control should possess :) Vertical Orientation     Both in our forum and support system we have received numerous requests for vertical orientation of the CoverFlow control. That is why, with our 2009...

Sometimes when using a Docking control and implementing complex UI with it we need to add some custom rules about allowing some panes to be docked in some parts of the application and to disallow them to dock to other parts. As this behavior is quite complex itself, we’ve decided to enable some scenarios to be available in XAML in a declarative way (the more static scenarios) and some scenarios to be available only through the code-behind.   In this post I will guide you through some simple steps that will show you how you could use both approaches. First of all...

Using FixedDocument, DocumentViewer and PrintDialog you can easily create your own print and/or print preview for RadGridView for WPF. I’ve made two extension methods Print() and PrintPreview() to illustrate how to turn the grid into a print friendly document in few lines of code: … public static void PrintPreview(this GridViewDataControl source) { var window = new Window() { Title = "Print Preview", Content = new DocumentViewer() ...