Please excuse us for the inconvenience caused.
The consumption of ODP.NET, Managed Driver is performed through a few modifications in the config files of the applications that utilize Telerik Data Access. Prior to them, you need to have the driver installed and configured. The requirement on the Telerik Data Access side is the version of the driver to be 18.104.22.168
. The following steps will guide you through the process:
1. In case the driver is not already at your disposal, the Oracle packages that distribute it are listed and available for download in this article
2. The An Easy Drive to .NET
article contains a tutorial for installing and configuring the driver according to your scenario. The sections in it that you may find of interest are: Installing ODP.NET, Managed Driver
, and Networking Configuration with ODP.NET, Managed Driver
3. To utilize the driver in the applications, which use Telerik Data Access, you need to provide Oracle.ManagedDataAccess.Client as a value for the providerName attribute in the connection string used for instantiating the context. For example:
"data source=XE;user id=X;password=X"
At this point, make sure to provide the specified providerName value not only in the config files of the projects that hold Telerik Data Access models, but in the config files of the projects, which consume them, as well. This setting is obtained by Telerik Data Access during runtime and the respective driver is loaded.
4. To test the configuration, you can use the Modules
window in Visual Studio during a debug session of the data access layer.
Additionally, let me assure you that the update of our documentation with the relevant information is already in process. Once it is available, I will make sure to notify you in this thread.
I hope this helps. In case you need further assistance or have additional questions, do not hesitate to get back to us.Regards,
OpenAccess ORM is now Telerik Data Access
. For more information on the new names, please, check out the Telerik Product Map