Telerik blogs

Latest

  • Productivity

    JustCode – Color Identifier Basics

    Color identifiers make it easier for developers to quickly read and understand the code on screen.  One of the many features provided by JustCode is the ability to colorize additional items that Visual Studio does not allow you to colorize by default.  The colorization of items such as methods, properties, events, variables, and method parameters can easily be tweaked to your specific needs. Enable / Disable Color Identifiers In the recent release, we turned this option on by default.  You can enable/disable code colorization by going to the JustCode menu in Visual Studio, selecting options, then selecting the general section in...
    April 26, 2010 1 min read
  • Productivity

    Working with multiple interfaces on a single mock.

    Today , I will cover a very simple topic, which can be useful in cases we want to mock different interfaces on our expected mock object.  Our target interface is simple and it looks like:   public interface IFoo : IDisposable {     void Do(); } Our target interface has an IDisposable implemented. Now, generally if we implement it in a class , we have to implement the whole of it [which is quite logical] and that should not wait for any extra calls or constructs. Considering that, when we are creating our target mock it should also implement all the dependent interfaces for us as well.   Therefore,  as we are creating...
    April 26, 2010 1 min read
  • Productivity

    Validating Your Domain Model

    With the Q1 Release of the Telerik OpenAccess ORM we introduced the new Visual Designer for OpenAccess. In a nutshell it’s a drag-and-drop editor that visualizes the mapped classes and their relationships. It is a great improvement and people are often stunned by it. One of the coolest features that it presents though is often overlooked. OpenAccess gives you the possibility of validating your model. Note that this is extremely helpful due to the fact that you are able to build your solution with an invalid model and then get errors in the runtime. On top of that it also suggests...
    April 26, 2010 2 min read
  • Productivity

    Looking at the Telerik OpenAccess ORM Visual Designer Toolbox

    The Telerik OpenAccess ORM Visual Designer provides toolbox items that one can use to update and fine tune the persistence model and how the entity classes will behave. Inheritance - like other objects, the mapped entity classes can be used in inheritance scenarios and can be derived from other classes. The Telerik OpenAccess ORM provides the power of inheritance to the data access layer. Classes in an inheritance hierarchy can be mapped to the same table (flat mapping) or to different tables (vertical mapping and horizontal mapping), or a combination of two strategies (mixed flat and vertical). The Telerik OpenAccess ORM Visual...
    April 25, 2010 2 min read
  • Productivity Reporting

    Using Telerik Reporting in a WPF application

    Now that Telerik Reporting provides WPF support, let's see how to use it (a video on this topic is available as well): Creating the application Install RadControls for WPF 2010 Q1 SP1 (download | release notes). Install the corresponding Telerik Reporting version. Create a new WPF application project in Visual Studio Add references to the following Telerik RadControls for WPF assemblies: Telerik.Windows.Controls Telerik.Windows.Controls.Input Telerik.Windows.Controls.Navigation Telerik.Windows.Data NOTE: It is possible that the RadControls for WPF assemblies have a greater version than the one against which the WPF Report Viewer control was built. In this case you have to add appropriate assembly binding...
    April 23, 2010 2 min read