Telerik OpenAccess ORM ObjectScope comes packed with all the events that are needed for managing the lifecycle of your persistent objects. You have events for Add, Remove, Refresh and Update actions. They come in –ed and –ing flavors which would mean that you can successfully iterate with your data before the changes have been made (-ing events) and after the changes have been done(-ed events) . You can subscribe to any or all of them and successfully perform some business logic over your persistent objects. Here is a basic implementation of a generic (in terms of availability for both ObjectScope and ObjectContainer)...

Perhaps nobody uses every bit of keyboard navigation when it comes to menus. I bet that there aren’t many of you who use F10 to activate the menu. You nevertheless expect our RadMenu to support keyboard navigation out of the box for the very few of your clients who are using the full set of navigation commands. Full keyboard support will be available in the next internal build so that you folks can give it a go: you will get accelerators, mnemonics, F10, and of course, the arrows and enter/escape keys support. The best part is that all commands will be internally...

Every now and then we receive requests / inquiries which wordings may vary, but basically all come down to the same thing – my chart space is limited, how to optimize the content of the ChartArea so my data does not look so squashed? One possible solution that works in some scenarios is to hide the legend altogether. Today we will propose another option for those of you who are looking for a less “radical” remedy – display the ChartLegend as a ToolTip on demand. Actually, this is quite easy to achieve with the ToolTipService class provided by WPF /...

digg_url = "http://www.stephenforte.net/PermaLink,guid,e137f5a7-7bea-4722-9359-5f830d95e691.aspx";digg_title = "Using WCF for Silverlight Development with Telerik OpenAccess";digg_bgcolor = "#FFFFFF";digg_skin = "normal";digg_url = undefined;digg_title = undefined;digg_bgcolor = undefined;digg_skin = undefined; Microsoft’s Silverlight 3.0 is a great new platform for building line of business applications. With every new technology advancement, we always seem to lose something. With Silverlight we lose the dirt simple data access since Silverlight does not support System.Data.SQLClient and talking to a database directly. This forces us into a service oriented architecture and an asynchronous model. While this is definitely a best practice, it sometimes takes a little getting used to. With Silverlight we have to wrap up our data access layer into WCF services. (Or Astoria, RIA Services, or something similar.) It is also pretty standard to use some kind of ORM like the Entity Framework...

You are probably aware that one of the great new features coming up with the WebUI Test Studio v2.0 is the Silverlight automation support! Yes, that’s correct – you will be able to record all your tests against any Silverlight application as easy as you currently generate the ASP.NET tests. As you might expect we are also working on the RadControls for Silverlight translators. They will let you automate the RadControls for Silverlight components out-of-the-box. I’ve just captured a snapshot of the RadTreeView translator providing some helpful verification tasks. It is taken from the live demo here. While organizing ...