As Q3 2013 of Telerik OpenAccess ORM is already live, we are proud to present the variety of enhancements
that it will bring to your development process.
OpenAccess ORM was already usable with multiple models, as long as each of them is defined with a unique connection string. Each model had a separate underlying database, using a separate set of metadata. With the new release, you can easily split one database into several Domain Models without the complexity of several connection strings, and OpenAccess will merge the metadata for you and use only one underlying Database object! Furthermore, with the new CacheKey parameter, you have more control over that behavior and can easily control which models should be used in an aggregated manner, and which should be separated.
Do you have long running queries or bulk operations that do not fit into the default timeout settings? With the new release the Command Timeout is fully configurable, both on a global level and for each separate query, offering you new opportunities to fine-tune your application.
Navigational Properties Naming Settings
Many of you have asked us to make the navigational properties naming flexible in order to provide more meaningful names for scenarios where two associations exist between a given pair of classes. Previously, OpenAccess Visual Designer used to resolve such cases of duplicated navigational property names in a standard way - adding "1" as a suffix of one of the properties. In Q3 2013, you have a complete new Model Settings tab for navigational properties naming, which allows you to use not only the class names but also the foreign key columns for naming the reference and collection properties.
OpenAccess.Core NuGet Package
The OpenAccess.CodeFirst NuGet has already been live for over an year, helping you to easily add the needed references to OpenAccess ORM data layer project, defining your persistent entities. Now you also have the same help for the projects that are just referring to your data layer, without defining new entities - the OpenAccess.Core. It brings you just the bare minimum in order to be able to recognize the needed types, but without any reference to the OpenAccess Enhancer since this tool is only needed where persistent entities are defined.
Those are not all of the goodies we have prepared in the new release - take a look at the full list and download the release for free to try them out!