Release 4.2.0

DataDirect Connect for ADO.NET Release 4.2.0

Only 100% managed code architecture for connectivity to Oracle, DB2, SQL Server, and Sybase using ADO.NET. With the 4.2.0 release, our Oracle and DB2 Entity Framework data providers are now Entity Framework 5.0 compliant. This update brings new functionality including:

New Features in ADO.NET Entity Framework Data Providers

• Visual Studio 2013 Certification
• Lightswitch HTML5 Support
• Windows 8.1 and Server 2012R2 support
• Documentation updates

DB2 iSeries Entity Framework data provider

• Entity Framework 6.0 support, compliant with these new features:
  • Support for Code-Based Configuration.
  • Support for Code First Mapping to Insert/Update/Delete Stored Procedures.
  • Support for Configurable Migrations History Table.
  • Support for Connection Resiliency.

Oracle Entity Framework data provider

• Support for Oracle Advanced Security
• Support for Oracle Wallet
• Entity Framework 6.0 compliant with these new features:
  • Support for Code-Based Configuration.
  • Support for Code First Mapping to Insert/Update/Delete Stored Procedures.
  • Support for Configurable Migrations History Table.
  • Support for Connection Resiliency.

Sybase Entity Framework data provider

• Certified with SAP Sybase ASE 16
  

Notes, Known Problems, and Restrictions

Sybase Entity Framework Data Provider

The DataDirect Sybase Entity Framework data provider does not support the following Entity Framework features:

• Code-Based Configuration.
• Table Valued Functions and Enumerated Types.
• Model-First, that is, the ability to start with a conceptual model and create the database from it (see http://msdn.microsoft.com/en-us/data/ff830362.aspx for more information).
• Code First, that is, write the classes that make up your domain model and generate a database schema or map to an existing database (see http://msdn.microsoft.com/en-us/data/ee712907)
• Translating String.StartsWith, String.EndsWith and String.Contains to LIKE in LINQ to Entities.

Installing Using Multiple Product Keys

The installer has been modified to allow you to enter up to three product keys.

Installation Requirements

• You must be a system administrator or have update privileges for the Registry key [HKEY_LOCAL_MACHINE]. These privileges are required to update the Registry with the new data providers being installed. See your system administrator if you are unsure.
• You must run the Setup program from the machine on which you are installing the product. You cannot run the Setup program from a network location to install the product on your local machine.

Installing on a Machine With Earlier Versions of the Data Providers

• DataDirect Connect for ADO.NET 4.1 can exist on the same machine with earlier released versions of DataDirect Connect for ADO.NET and DataDirect Connect for .NET (GA version or with any of the patches or service packs), but cannot be installed in the same directory.

Visual Studio 2008 Issues

• The context menu Item for Tables called “Show Table Data” is missing in Visual Studio 2008. The context menu with same behavior appears in Visual Studio 2008 with a different name, "Retrieve Data".
• Installing Visual Studio After Installing the DataDirect Connect for ADO.NET Data Providers

  If you install the DataDirect Connect for ADO.NET data providers on a machine that does not have Visual Studio installed, and later install Visual Studio, you must use the Administration Tool in the DataDirect Connect for ADO.NET 4.1 program group, and select the Visual Studio Integration tab.

Visual Studio 2010 Issues

• Installing Visual Studio After Installing the DataDirect Connect for ADO.NET Data Providers

  If you install the DataDirect Connect for ADO.NET data providers on a machine that does not have Visual Studio installed, and later install Visual Studio, you must use the Administration Tool in the DataDirect Connect for ADO.NET 4.1 program group, and select the Visual Studio Integration tab.

Visual Studio 2012 Issues

• Installing Visual Studio After Installing the DataDirect Connect for ADO.NET Data Providers

  If you install the DataDirect Connect for ADO.NET data providers on a machine that does not have Visual Studio installed, and later install Visual Studio, you must use the Administration Tool in the DataDirect Connect for ADO.NET 4.1 program group, and select the Visual Studio Integration tab.

Migration Notes

• The default value of the GrantExecute connection string property of the DB2 data provider is now True.
• The EnlistDistributedTransaction method of the data provider Connection object is obsolete. You can use the EnlistTransaction method introduced in the .NET Framework 2.0. We recommend that you use System.Transaction for all transactions instead.
• For the DB2 data provider, the Security Mechanism connection string option and the corresponding DB2ConnectionStringBuilder property SecurityMechanism are marked as obsolete. They are replaced by the Encryption Method connection string option and EncryptionMethod ConnectionStringBuilder property.
• For the SQL Server data provider, the Integrated Security connection string option and the corresponding SQLServerConnectionStringBuilder property IntegratedSecurity are marked as obsolete. They are replaced by the Encryption Method connection string option and EncryptionMethod property.