Telerik blogs
  • Release

    OpenAccess ORM Q2 2011 Will Feature a Profiler, Check Out the Roadmap

    Todd Anglin's blog on how to trust the SQL an ORM tool produces stirred quite a bit of attention from the community, which also pushed us to action. As a result, we are happy to announce very exciting news on the next version of Telerik OpenAccess ORM, due this summer. Telerik OpenAccess Q2 2011 will come with a built-in Profiler, which will open the "black box" of its operations and will give you an insight on how to optimize its behavior. This tool will also provide great assistance to developers who have decided to not use an ORM tool on the premise...
    April 27, 2011
  • Productivity

    Setting advanced runtime options

    There are various properties that govern how the OpenAccess ORM runtime behaves. The default values for these settings usually suffice for most situations. In case you need to tweak some settings, this can be done via the ‘Backend settings’ tab in the ‘Model settings’ dialog available in the Visual Studio designer. These options are broadly divided into 4 categories (here you can find more information about this dialog and the settings available): Runtime configuration Tracing & logging Second level cache Connection pool When any setting is changed in this dialog and the .rlinq file is saved, OpenAccess generates the appropriate code to set...
    April 20, 2011
  • Release

    Upgrading OpenAccess Forward/Reverse Mapping Projects to Q1 2011 Fluent API and Visual Designer Projects

    Back in Q2 2010 Telerik OpenAccess ORM introduced an Upgrade Tool which converted projects created with the old Reverse Mapping Wizard to use the Visual Designer. Well, Q1 2011 introduces a much improved second version of this useful tool. What are the improvements? Unlike the previous version that supported reverse-mapped projects only, the new Upgrade Tool can convert projects built upon Reverse and forward-mapped projects. And the best part of it is that, besides the Visual Designer, is that it utilizes the updated full-featured Q1 2011 Fluent Mapping API to achieve this. To upgrade your existing project and continue your development with the...
    March 23, 2011
  • Productivity

    Converting an Entity Framework Model to the OpenAccess Domain Model (Q1 2011)

    Now that Linq-to-SQL is not going to be developed any more, it seems developers are left with little choice as to what ORM to use for their next projects. The ADO.NET Entity Framework seems to have become the ORM of choice for most Microsoft developers, who want to address the impedance mismatch across various data representations, but although very good and quite powerful, it falls short on some important characteristics of modern-day development: Visual Mapper/Entity Designer with advanced capabilities; Lack of native support for databases different from SQL Server; Release cycle of 2-4 years; Advanced/dedicated technical support; No built-in caching layer; We are sure that code-first...
    March 21, 2011
  • Productivity

    A simpler ObjectKey

    As existing users might have experienced , handling the identity of a persistent object in OpenAccess can get complicated at times especially when it comes to a type with composite identity fields. With an aim to simplifying this aspect we worked on the ObjectKey API to make it easier to comprehend and to use. This blog post describes the API in brief, it’s intended usage and how existing code can be migrated.   The ObjectKey The ‘ObjectKey’ is the new entry point for working with a persistent object’s identity. The ‘ObjectKey’ for a persistent object can be obtained form the runtime or if...
    March 21, 2011