Telerik OpenAccess ORM (formally Vanatec OpenAccess) - .NET/AddIn - V4.4

Descrizione generale | Prezzi e licenze | Valutazioni e download | Compatibilità | Dati autori | Recensioni | Forum | Sommario

Ti preghiamo di notare che le informazioni su questi prodotti non sono disponibili in italiano.
Map your objects to your relational data. Telerik OpenAccess ORM (formally Vanatec OpenAccess) has been designed for bridging the gap between object-oriented programming and relational data management and access based on the .NET framework. Tightly integrated into Microsoft Visual Studio, OpenAccess saves 30% coding efforts and provides Object Relational mapping (O/R mapping, O/RM, ORM) features like transparent persistence, polymorphism, query browser, reverse mapping, Database Independence with SQL Server, Oracle, MySQL, Firebird, Sybase SQL Anywhere, Advantage Database Server and disconnected data support.

Vanatec OpenAccess will be rebranded to Telerik OpenAccess ORM and will be available individually or as part of the Telerik Premium Collection. This will happen with Telerik’s upcoming Q3 release, scheduled for November 5, 2008. The initial release of OpenAccess as a Telerik product will also introduce key new features and effortless integration with the Telerik UI product lines, here are some highlights about what is coming up on November 5th:

Telerik OpenAccess ORM - Q3 2008 (Nov 5th, 2008)

• improved design time experience
• improved LINQ support
• integration with Telerik RadControls
• the new version is also Java-free (the dependency to J# libraries has been removed)

What's New in Telerik OpenAccess ORM (formally Vanatec OpenAccess) Build 4.3?

Using connection specific references section not working

There is now an optional references section under the connection element. This allows to specify a set of assembly references to follow for a specific connection id and can be necessary when certain application modules need to be loaded on a per-connection specification.

The ResolveProxyEventArgs structure was modified.

The ResolveProxyEventArgs structure was modified so that the request to resolve multiple proxies can be expressed; the ProxyIdentity property returns an array of IObjectId instead of a single IObjectId now. Also, the boolean property WriteAccess was replaced with the Operation property returning an enum which indicates the attempted operation, including Delete.

Fetch Groups UI added to the Mapping dialog
The mapping dialog now contains an additional tab for defining fetch groups. Fetch groups can be defined for persistent classes, using the non-transisent fields of that class. The App.config file contains all the fetch groups related entries .

Support for Sybase SQL Anywhere
OpenAccess now supports Sybase SQL Anywhere Version 10. SQL Anywhere 10 be used with forward mapping and reverse mapping. Although only available for .Net 2.0, System.Transactions can currently not be used as the iAnywhere provided ADO.NET driver does not support enlistment.

64 bit support
Microsoft has produced a new J# runtimes system named Second Edition for .NET 2.0 and above. The main feature of this is that it is 64 bit compatible. With the 64 bit version of the J# runtime system, OpenAccess runs on all supported 64 bit machines.

Single Field Identity
Single Field Identity provides a mechanism where one exclusive field holds the identity information. The description of this field is done by the [Persistent] attribute. The property IdentityField defines the name of the field used.

Support for the Advantage Database Server 8.1
OpenAccess now adds support for Advantage Database Server (ADS) 8.1.
In order to use a database on an ADS remote server, you need to have the Advantage Data Provider installed on the client machine.

Reverse Engineering - Implementation of Partial Classes
The Reverse Engineering Wizard can now generate "partial classes". Partial Classes can be generated by checking the 'Generate Partial Classes' checkbox on the 'Class Generation' tab.

Classes get generated in two files - the 'designer' file and the 'main class' file. The designer file gets added as a child item of the 'main class' item in the solution explorer.

OVERVIEW

Telerik OpenAccess ORM (formally Vanatec OpenAccess) is an object-relational mapping tool, fully integrated into Visual Studio and featuring:

• Transparent Persistence
• Polymorphism
• Forward-, Reverse-, Roundtrip-Mapping
• Object Container for Disconnected Scenarios
• Flexible Mapping (flat, horizontal, vertical and mixtures)
• Mapping in the middle (keeps your code and your database clean)
• Support LINQ, OQL and SQL as Query Language
• Fetch Plans for high performance
• Distributed Caching for unlimited scalability
• Query Browser
• Optional Wizards for multiple configurations, settings and definition
• Visual Studio 2008, 2005; .NET 2.x, 3.x
• Database Independence with SQL Server, Oracle, MySQL, Firebird, Sybase SQL Anywhere, Advantage Database Server
• Free license for free database (eg SQL Server Express, Oracle Express, MySQL, Firebird) running on local machine

Object-relational Mapping for .NET

The usual DataSet in .NET applications creates problems for developers who want to use the full power of object-oriented programming to solve their business problems. Using business objects to organize the behavior they are calling on a proven approach.

However this architectural approach is difficult to reconcile with DataSet’s rigid row and column structure. Instead of DataSet, use Vanatec’s object-relational mapping to transparently map between your business objects and your relational tables.

With Telerik OpenAccess ORM (formally Vanatec OpenAccess), you’ll find all of the O/R mapping essentials built right in: transparent persistence, database flexibility and database independence, reverse mapping, disconnected data support. And most importantly, it separates the storage details from your object model, simplifying your code and boosting productivity.

Transparent Persistence
Telerik OpenAccess ORM (formally Vanatec OpenAccess) is an object-relational mapping persistence framework that offers transparent persistence through post-compilation code enhancement. As such, adding persistence functionality is non-intrusive to the object model. Custom attributes are used to assign attributes to classes. With custom attributes classes can be declared as persistent, and for example indexes can be defined for class fields. With Telerik OpenAccess ORM (formally Vanatec OpenAccess), classes do not have to inherit from a specific base class or implement a specific interface to be persistent. Telerik OpenAccess ORM (formally Vanatec OpenAccess) does not put any restrictions on the object model and supports inheritance, interfaces and .NET Framework collections.

Database Flexibility & Database Independence
You don’t live in a vacuum, and neither will your .NET application. Using Telerik OpenAccess ORM (formally Vanatec OpenAccess), your application easily runs with various database branches, various table layouts, or even various database technologies. Only one single file needs to be edited.

Connecting your .NET application to different databases is easy in part because Telerik OpenAccess ORM (formally Vanatec OpenAccess) separates the storage details from your object model. That simplifies your code and boosts productivity on the one hand. On the other, it means more flexibility: Working with various databases, changes in the table layout or data model don‘t cause changes in the object model and vice versa.

Reverse Mapping with Legacy Databases
Telerik OpenAccess ORM (formally Vanatec OpenAccess) detects your existing legacy data model the moment you connect it, creates object models, and even lets you edit the object model exactly how you want it.

The reverse mapping experience begins the minute you connect your Visual Studio project to the legacy database using the Reverse Mapping wizard. Like magic, Telerik OpenAccess ORM (formally Vanatec OpenAccess) recognizes the data model and creates an object model. Then you can start developing your new .NET application.

Disconnected Data Support
Whether you’re thinking of mobile devices, Web applications, or replications, you need disconnected data management you can count on anywhere, anytime. In these cases, it isn’t possible to maintain a database connection for the duration of a transaction. For this situation, Telerik OpenAccess ORM (formally Vanatec OpenAccess) offers ObjectContainer. It frees objects from databases and uses optimistic transactions. It tracks which objects have been changed or are new. A callback lets you resolve any conflict.

Tight Integration with Microsoft Visual Studio
Using Telerik OpenAccess ORM (formally Vanatec OpenAccess) is easy in part because you can continue using the same application you already know - Microsoft Visual Studio. And when it comes to data access, simply choose OpenAccess in the Visual Studio menu. Fully integrated into Visual Studio, Telerik OpenAccess ORM (formally Vanatec OpenAccess) takes action on the data access and it gives you the programming productivity you need to develop sophisticated applications in no time.