7 Reasons to Choose OpenAccess ORM over Entity Framework
1. New features 3 times per year
It's a race - with technology and competition. And we like to be ahead, so that you are ahead with the newest tools. We never stop - 3 major and at least 3 service releases per year for every product. Weekly builds are also available so that your problems are eliminated right away.
2. The industry-leading Telerik tech support
Developer tools are useless without technical support. And we offer the very best one. Even the free community support that accompanies every copy of OpenAccess ORM is top notch. Actually that's a key reason why people choose Telerik. We are there when you need us most – on the support system, on the phone or through remote assistance sessions. You don't get just DLLs, but data access solutions. Whatever your question, one of the developers who built OpenAccess will get back to you to make sure you will meet your deadline.
3. You get one-click access to Web Services “out of the box”
Generate WCF Data Services or ASP.NET Web API services based on your data context using simple wizards and get your N-Tier solution up and running right away! We can even create an entire Data Transfer Objects layer for you, or help you manage your entities in the different application layers using the flexible Attach/Detach functionality.
4. Batch-update your data model classes & properties in a single operation
Creating your data model is always easy, but the hidden cost sometimes lies in the continued maintenance over time. With the help of the OpenAccess Batch Operation Dialog refactoring of your data models is easier than ever. Utilizing the Batch Operations functionality, developers can efficiently make updates to large Domain Model by modifying hundreds or thousands of classes in a single operation. It is as easy as pie.
5. It’s so easy to convert legacy data layers to Telerik OpenAccess
Easily convert your existing Entity Framework, LINQ to SQL or even NHibernate projects to quickly get it running into OpenAccess ORM and get armed with all the Telerik ORM’s extended functionality. Use the convenient converting wizards and our extensive migration guides to save yourself tons of coding and development hours as well as prevent headaches.
6. Built-in support for 20+ databases
Telerik OpenAccess ORM works equally well with more than 20 databases (and new ones are constantly added), such as Microsoft SQL 2012, SQL Azure, Oracle, and more (see below for more information). All major features, such as stored procedures and functions, views, and concurrency control are supported for all databases.
7. You face short learning curve
The Telerik Software Development Kit (SDK) for Telerik OpenAccess is an easy to use resource browser for all things OpenAccess. It includes auto-configured end-to-end solutions and relevant information for developers to get started and quickly integrate Telerik OpenAccess ORM in their applications. Find out more and get it.
You can also dive into our rich collection of OpenAccess videos available on Telerik TV that will help you get started from day one saving you hours of documentation reading.
OpenAccess and Entity Framework 5 Comparison
Legend:
- Full support
- Limited support
- Not supported
- n/a- Not applicable
Features | Feature | OpenAccess ORM | Entity Framework 5.0 |
| Visual Designer | Yes | Yes |
Fluent Mapping API | Yes | Yes |
| | Yes | Not Supported |
| | Limited | Yes |
LINQ support | Yes | Yes |
| | Yes | Not Supported |
| | Yes | Not Supported |
Stored procedures & functions support | Yes | Yes |
| | Yes | Limited |
| | Yes | Not Supported |
| | Yes | Limited |
Custom Types Framework | Yes | Not Supported |
DDL Capabilities | Yes | Yes |
DML Capabilities | Yes | Yes |
Spatial Data Types | Yes | Yes |
| | Yes | Not Supported |
Command line generation tools | Yes | Yes |
.NET 3.5 Support | Yes | Not Supported |
.NET 4.0 Support | Yes | Yes |
.NET 4.5 Support | Yes | Yes |
Optimistic Concurrency | Yes | Yes |
Pessimistic Concurrency | Yes | Not Supported |
Built-In L2 Cache | Yes | Not Supported |
Advanced Connection Pooling | Yes | Not Supported |
Pure XML mapping | Yes | Not Supported |
Pure Attributes mapping | Yes | Yes |
Data Transfer Objects (DTO) | Yes | Yes |
Self-Tracking Entities | Not Supported | Yes |