• .NET

    The many localizations of RadEditor and RadSpell

    February 06, 2009 Share
    Did you know that there over 25 localized versions of RadSpell's dictionaries (30, to be exact)? Did you know there are over 10 localizations of RadEditor? When you're building a global site, you often need to support a number of languages, and thanks to Telerik's outstanding community, we are able to offer a huge range of localizations for the RadControls- especially those controls which depend heavily on localized strings. Not all controls require localizations- a RadSlider or ColorPicker, for example, communicate their UI without any built-in strings. Even controls like RadGrid don't have much need for localization. Other controls- like...
  • .NET

    Optimization Tips: RadInput vs. RadInputManager

    January 29, 2009 Share
    In the Q3 2008 release, Telerik introduced a new control to the RadControls for ASP.NET AJAX suite called RadInputManager. Like RadInput, it is designed to enable you to provided textboxes to your users that give real-time validation and feedback based on the entered text. The big difference with RadInputManager, though, is that you don't have to add lots of Telerik Input controls on your page to get this real-time feedback. Instead, you can quickly convert "standard" ASP.NET TextBoxes to RadInput textboxes via the RadInputManager configuration- similar to how you can use RadAjaxManager to quickly ajaxify your page without littering it with...
  • .NET

    Optimization Tips: RadCompression Module

    January 28, 2009 Share
    Welcome back to the ongoing Optimization Tips series. It's been a while since the last installment, so it's high-time we took a look at more tips and tricks for optimizing your Telerik-powered web applications. In this the seventh article in this series, we'll take a look at Telerik's brand new RadCompression HttpModule and try to gain a deep understanding of how this tool can help improve application performance. Some of the concepts in this article build on things we've discussed in previous installments, so I encourage you to read the earlier articles before reading this if you have not already done so....
  • .NET

    Simplifying OpenAccess Scope in ASP.NET with HttpModule

    January 20, 2009 Share
    Whenever you start working with a modern ORM tool, one of the biggest challenges is figuring out how to manage the "scope" (or sometimes called "context" or "data context"). It is this transactional space where the ORM tool keeps track of changes being made to "persistent objects" in your application so that they can be saved to your "persistence layer" (usually a database) when you're ready to commit them. But figuring out when to create a scope, when to close it, and all the annoying problems that result from closing a scope too early can be very frustrating, and they...
  • .NET

    Improving OpenAccess ObjectScopeProvider for Runtime Connection Config

    January 09, 2009 Share
    Phew! That's a long blog post title, but hopefully it clearly conveys what I'm about to show you. In my last post, I talked about where you should set your OpenAccess database connection strings. I showed you how you can define multiple database connections in your web.config (or app.config), simulating the idea of having a unique connection string for DEV, TEST, and PROD environments. So now that you have your connection strings set in a way that is easy to maintain, you need a way to easily to tell your OpenAccess persistent classes to use a specific connection at runtime. Let's look...