LINQ and Full Oracle Support
Unfortunately, it appears that Microsoft and Oracle still have not found a way to the light. The latest Beta 2 is still locked to only support provisioning objects from MSSQL data sources. Even if you have the Oracle client loaded, use OLEDB (or Oracle, tried both), and have added the database to your Data Connections list, you get an error when you try to drop a table on to the builder.
“The selected object(s) use an unsupported data provider.”
Clicking help tells us that:
This message appears when you drag items that do not use the .NET Framework Data Provider for SQL Server from Server Explorer/Database Explorer onto the .
The O/R Designer supports only data connections that use the .NET Framework Provider for SQL Server. Only connections to Microsoft SQL Server or Microsoft SQL Server Database File are valid.
To correct this error:
Add only items from data connections that use the .NET Framework Data Provider for SQL Server to the O/R Designer.
So, for now, my class libraries will remain in tact—you can LINQ pre-created objects coming from Oracle, just not directly to Oracle tables. I checked CodePlex and didn’t see anything yet, but I’m sure it will get there. Enough .NET developers still code against Oracle that without support, it will be hard for organizations to buy into the transition (no one wants half–and-half coding).