. .
Personal details
Community details
Overall rating
Other comments
3
This software doesn't do what I want.
0
You're not the only one with this complaint.
We have found that this software is suitable for most people.
You need to agree to the terms and conditions of the software before it can be fully used.
You can report that this software does not do what you want.
We value your feedback!
Currently, we only support. . .
Looking for more?
VitalSource has many more DRM converters available on all the digital content you love to read, watch, listen to, or play. Find your content below.
Find your content
The below table of content covers all the Converter available on our site. However, our site may not be able to process all the content and/or formats on the site. You can browse our other converters by clicking on the green "Advance search" button on the top right corner of this page.Q:
Entity Framework With Oracle.OracleClient Connection for NoSQL
We are currently converting from SQL Server to Oracle in our web application. We are using Entity Framework with Oracle.OracleClient as the provider. We are using custom migrations to handle the initial database creation, including data context creation.
There are currently 2 problems with our migrations.
The first is that I cannot get Oracle.OracleClient to work with SQL Server Express. It requires I register the provider and set the provider to Oracle.OracleClient. This is fine, but when I try to use this connection in the ORM (model first), I get this exception:
Unable to determine the providerName for provider factory of connection.
The second is that we are now using a NoSQL database (MongoDB) for the majority of our database interactions. Our custom migrations have these problems:
Oracle.OracleClient doesn't work with MongoDB.
It can't figure out how to create a DbContext.
Does anyone have any idea how to connect to NoSQL databases in Entity Framework with custom migrations?
A:
The reason the 'Unable to determine the providerName for provider factory of connection.' error is happening is because the default provider factory of Entity Framework 4 has been set to Microsoft.Data.SqlClient. In
Related links:
Comments