Hi Jonathan Simmons,
This problem is already fixed and the fix will be available in the internal build that we are planning to release in a few days. In the meantime please use the following workaround:
- Select any not-oracle connection that you can create on page one of the wizard;
- On page two do not select any tables; Click Yes to confirm that you do not want to add any tables to the model; Finish the wizard;
- Open the App.config file of the project and without changing the connection string name, modify the connection string to the actual Oracle string you want to use. For example:
"data source=XXX;persist security info=True;user id=YYY;password=ZZZ"
Make sure the providerName attribute is set as shown above, this is the ODP.NET client provider.
- Open the empty .rlinq diagram and with a right-click on the Model Schema Explorer window, open the Update from database dialog; Then you should be able to add your oracle tables to the model and map them to classes by dragging them from the Schema Explorer to the design surface;
We are sorry for the inconvenience this might be causing.
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Public Issue Tracking
system and vote to affect the priority of the items.